-
Notifications
You must be signed in to change notification settings - Fork 3
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
make lock_pip
and dataflow-versions.txt conflicts
#1939
Comments
google-cloud-core:
Fixed by adjusting |
tenacity:
Fixed by removing from the dataflow versions output |
packaging:
removed from dataflow-versions.txt output |
Seems to work fine if I don't delete the constraints file before recreating. I'm guessing it just updates a minimal set with the new requirements. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was trying to recreate a constraints file with some additional packages for a pytorch environment and was running into incompatibilities between our pip requirements and the beam image values.
What's the deciding protocol for which version is correct?
Overall, it seems like pip-compile doesn't take into account some more flexible constraints from different files.
Steps to reproduce the problem:
rm constraints.txt
make lock_pip
The text was updated successfully, but these errors were encountered: