-
-
Notifications
You must be signed in to change notification settings - Fork 611
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
Better explain role of existing requirements.txt
#1369
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1369 +/- ##
=======================================
Coverage 99.67% 99.67%
=======================================
Files 33 33
Lines 3037 3037
Branches 327 327
=======================================
Hits 3027 3027
Misses 5 5
Partials 5 5 Continue to review full report at Codecov.
|
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 👍
This commit adds an explanation of the role of existing requirements.txt files to the README. I found this very unclear and opened #1358 because of my confusion. The existing short note that requirements.txt "might interfere" didn't really help me. I'm not sure how common my confusion is, but I hope my changes makes things clearer to new users (assuming what I've written is in fact correct!) (In addition to my additions, I moved the "Updating requirements" section up in the doc, since it seems like a core workflow.)
Thanks @mikepqr 🙏🏻 |
Thank you for your help! |
requirements.txt
This commit adds an explanation of the role of existing requirements.txt
files to the README.
I found this very unclear and opened #1358 because of my confusion. The
existing short note that requirements.txt "might interfere" didn't
really help me. I'm not sure how common my confusion is, but I hope my
changes makes things clearer to new users (assuming what I've written is
in fact correct!)
(In addition to my additions, I moved the "Updating requirements"
section up in the doc, since it seems like a core workflow.)
Changelog-friendly one-liner:
Contributor checklist