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
Fix requirement files and package data #2156
Conversation
Sorry for the spam guys. I'm walking to the coffee machine as we speak to hopefully prevent more commits 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
# Tools used during development, prefer installing these with pre-commit | ||
black | ||
pre-commit | ||
pylint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pylint cannot be installed with pre-commt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"prefer installing these with pre-commit", this is not possible for pylint as it's a system hook.
requirements_minimal.txt
Outdated
@@ -0,0 +1,8 @@ | |||
# Tools used when releasing | |||
contributors-txt>=0.7.4 | |||
tbump~=6.9.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbump~=6.9.0 | |
tbump~=6.9 |
I reviewed changes and they looks reasonable, but I'm not sure how to test this properly without a sdist release. Anyway, my workflow (packaging of Python projects for OpenIndiana) does not require perfect sdists because I can easily patch them (as I currently do with astroid 2.15.4), so if there will be something still not working as expected I'll report back. Thank you! |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2156 +/- ##
=======================================
Coverage 92.54% 92.54%
=======================================
Files 94 94
Lines 10783 10783
=======================================
Hits 9979 9979
Misses 804 804
Flags with carried forward coverage won't be shown. Click here to find out more. |
This makes the files installed.
|
@hroncok I always mess this up. How should we do this to prevent polluting the global namespace? |
Don't |
@hroncok Sorry for taking so long to respond. This has been constantly on my radar, but I really have no idea how to fix this. If I |
No, that's not expected at all. And I cannot reproduce it. See #2295 which works for me. |
Hmm that did seem to work. No idea why it didn't on initial try locally. Thanks for the help! |
Type of Changes
Description
Closes #2129
The first commit has been a pet peeve of mine for months. I really disliked how it was hard to see what you need to install when first opening the project. I hope this lay out is a bit more explicit.
The second commit adds the files as requested by @mtelka.
Tested with
pip install .
and the files ended up in the egg info. @mtelka could you test if this branch fits your needs?