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
The text was updated successfully, but these errors were encountered:
finn-ball
changed the title
Ability to define your own requirements lock file or python version for third party pip dependencies
Thirdparty pip dependencies override root project's pip dependencies
Mar 11, 2024
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!
🐞 bug report
Affected Rule
Is this a regression?
Between old
WORKSPACE
rules andbzlmod
, potentially yes - so long as you knew the order you were defining dependencies.Description
A third party project called foo uses
rules_python
andbzlmod
to bring in pip dependencies:This dependency is implicitly used as part of a library this third party defines. This
requirements_lock.txt
uses a pip modulematplotlib
at v1.My root project uses the pip extension and its own
requirements_lock.txt
file to bring inmatplotlib
at v2.If I depend on the
@foo
project:The target will now use
matplotlib
at v1. Even though my root project specifically asks for v2.🔬 Minimal Reproduction
Follow the examples in here
🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_python version:
Anything else relevant?
The text was updated successfully, but these errors were encountered: