You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update compile_pip_requirements to support requirements.in files from multiple external repositories #624
I have some external repositories that have some rules backed by python targets and have some requirements. Instead of needing to create multiple pip_parse or pip_install repositories, I would like to generate a requirements.txt file that has all the necessary packages so I don't end up downloading things multiple times.
Describe the solution you'd like
I would like to be able to pass the requirements.in files to compile_pip_requirements and have that inject them as -r {requirements} before compiling.
Have you considered any alternative solutions or workarounds?
Open to ideas but I'd like to easily be able to merge other sets of requirements into one collection (which is one of the benefits of being able to compile a locked requirements.txt file).
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_python!
Activity
UebelAndre commentedon Feb 17, 2022
Do I recall correctly that @mattem had sketched up a potential solution once upon a time?
github-actions commentedon Dec 11, 2022
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_python!
github-actions commentedon Jan 10, 2023
This issue was automatically closed because it went 30 days without a reply since it was labeled "Can Close?"
UebelAndre commentedon Jan 11, 2023
This is still desired.
I don't think
rules_pythongets so many issues that this bot needs to continually close them. This functionality should be disabled.build(deps): bump pytest-mock from 3.15.1 to 3.17.0 in /dev (bazel-co…