-
Notifications
You must be signed in to change notification settings - Fork 11
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 use of pip-compile
#1075
Fix use of pip-compile
#1075
Conversation
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.
A few suggested changes are requested. More testing is needed on the newly added Python manifest files. It may be that pip-compile
has an issue with the instances of manifests used during my testing...but I will check on that next week when I get back into this.
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.
It appears things are working now, albeit with some idiosyncrasies that may be helped with better documentation or error messages.
Keep `poetry` as the default generator for `pyproject.toml` files because it is very common. But allow the user to use `-t pip` for other backends (requires `pip-compile`)
The command is not run from the same working directory, so using relative paths was causing failures.
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.
With the new issues created to address the findings here, this LGTM.
This patch updates our usage of
pip-compile
to:requirements.in
,setup.cfg
,setup.py
, andpyproject.toml