-
Notifications
You must be signed in to change notification settings - Fork 12
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
Do not pollute site-packages #29
Comments
Hmm, this appears to be an unintended side effect of using poetry that I did not know about: python-poetry/poetry#2015 (comment) I will figure out how to fix this properly. Removing the |
…section, as this had unintended consequences of installing them into the site-packages directory instead of along side the package code. This is related to python-poetry/poetry#2015 . Since the LICENSE is available in the dist-info directory along side the package, then this is sufficient. Additionally, the python version classifiers will be automatically added by poetry from the version range specification in the tool.poetry.dependencies section, so no need to explicitly define them.
I have fixed this and released (ignore the failing build, coveralls.io API just failed) |
Note that this same issue will be in other libraries I maintain so likely the LICENSE file will still be there just from another library, if you're using something like pylint-django or prospector... I will go fix those now too. |
…e-packages directly instead of next the source, but will still be avialable in the .dist-info directory. See pylint-dev/pylint-plugin-utils#29
Currently,
LICENSE
andREADME.md
get installed into site-packages directory. This is bad, for obvious reasons.I used this patch to fix the problem:
The text was updated successfully, but these errors were encountered: