-
-
Notifications
You must be signed in to change notification settings - Fork 614
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
pip-compile requirements.in
produces a different output than the pre-commit hook.
#2034
Comments
Hi, thanks for the great work! I am also awaiting the release with #2011 included. |
Same issue here |
For me it works again with the newest pip... |
If I rollback to pip At the end I'm not sure what should be fixed where (pip ? pip-tool ?) I tried to play with |
I am using pip==23.3.2 and pip-tools==7.3.0 and it works as well. However, I feel your confusion. |
Since the upgrade to pip==24.0.0 I have this issue again 😒 |
@MartinRoth Do you have the issue with pip-tools >= 7.4.0? |
Hi @AndydeCleyre, currently I am using pip-tools==7.4.0 and pip==24.0 and it seems to work again. |
Thanks! Considering this resolved, then. |
I confirm also with latest using pip-tools 7.4.0, pip 24.0 and latest renovate 37.218.0 I don't see anymore any compatiblity issue. Thanks! |
In version 7.3.0
pip-compile requirements.in
produces a different output than the pre-commit hook.The is no issue after downgrading to 7.2.0.
Environment Versions
Steps to replicate
requirements.in
content:.pre-commit-config.yaml
content:requirements.in
filepip-compile requirements.in
Expected result
requirements.txt
should remain unchanged when running the 4th step.Actual result
requirements.txt
differs.diff
output:The text was updated successfully, but these errors were encountered: