-
-
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
Fix the output file for pip-compile with an explicit setup.py as source file #731
Fix the output file for pip-compile with an explicit setup.py as source file #731
Conversation
Codecov Report
@@ Coverage Diff @@
## master #731 +/- ##
==========================================
+ Coverage 86.33% 86.56% +0.23%
==========================================
Files 34 34
Lines 2129 2137 +8
Branches 303 302 -1
==========================================
+ Hits 1838 1850 +12
+ Misses 226 224 -2
+ Partials 65 63 -2
Continue to review full report at Codecov.
|
23793fd
to
6dd97c2
Compare
Since a branch |
05a59ce
to
4304584
Compare
Hello @blueyed. Gentle ping. Is everything okay in the PR. Could you approve or request any changes if you'd like. |
4304584
to
682b184
Compare
I've resolved conflicts, rebased and squashed commits. I'll merge this as soon as tests are passed. @blueyed, thanks for your help! |
…ce file The command `pip-compile setup.py` generates a `setup.txt`, but it should be a requirements.txt file.
682b184
to
37ae661
Compare
The `pip-compile setup.py --output-file=output.txt` ignores `--output-file` option and compiles to a `requirements.txt` file.
Fix a regression bug introduced in #731 PR
|
The command
pip-compile setup.py
generates asetup.txt
, butit should be a requirements.txt file.
Fixes #730.
Changelog-friendly one-liner: Fix the output file for pip-compile with an explicit setup.py as source file
Contributor checklist