-
-
Notifications
You must be signed in to change notification settings - Fork 574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for PEP 582 (Python local packages directory) #1697
Comments
For anybody finding this, workaround is to put the following into your config:
|
I'd be very surprised if any significant number of projects legitimately want Python imports inside of a |
This is implemented in develop and will be pushed to PyPI in the 5.9.0 release of isort |
Thank you! I won't submit this to black through since I don't use and dislike for “your not ready to embrace back” reasons. Somebody else will have to do that. |
When using flake8 for projects managed with PDM, which implements PEP 582 (Python local packages directory), I find a large amount of errors reported for files under the local packages directory like this:
While the
__pypackages__
directory is specified by the recent PEP-582, that PEP is currently draft status, so the name (and the entire feature) is guaranteed to stick around. Although PDM and PyFlow already use this convention and provide PEP-582 shims, they'd probably change if the PEP proves unworkable for some reason.FYI,
flake8
decided to close a similar request at GL/pycqa/flake8#681 noting that “we'll maybe reconsider this if [PEP-582] is accepted”.The text was updated successfully, but these errors were encountered: