Timothy Edmund Crosley
Timothy Edmund Crosley
isort intentionally does not wrap withing a single token for the following reasons: - it's very uncommon and generally already bad style to have such a long path in Python....
> The way I see it, module should either warn me about long import path when checking or have a max-line-length flag. A small point of clarification: isort is a...
@0lmer all those improvements sound good and would be accepted! Is this still something you could submit?
@piotrgredowski exactly those! The project would be to add a third option to replace imports.
If those constraints make it easier to create the initial implementation, I'm very comfortable with both being put in place. We'd just want to document it and make the error...
Do you have any more context? Do you mean for config options such as `known_first_party`? The following should work for that the same `known_first_party=modules` as the following * is implied
That's an interesting concept! It's not currently supported, but I'm open to support simple patterns (probably not full regex, but simple * support like shown)
This is not an isort specific issue. isort hasn't made any releases that change this behavior, and in fact hasn't made any release in some months. It also has no...
This is true for all literal / type sorts, and is why they aren't documented / advertised features, even though If they were in a good spot I would do...
Hi! So sorry you ran into this corner case! Older versions of Python didn't have implicit namespace package support, which allows namespaces to be created in a way that's statically...