-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
[Bug]: bazel-runfiles
pypi library does not work
#377
Comments
This is a rules_python issue I think, as the runfiles helper is walking up the directory structure to attempt to determine the runfiles root, which under the venv (or any other layout) is not correct. The diff here shows a potential solution, but I'm not clear if this is correct, or what repercussions this has, I imagine Windows will have something to say about it. Continuing the discussion with other rules_python maintainers. |
I'm getting this same issue:
|
What happened?
bazel-runfiles
library is unable to properly locate runfiles root when running underrules_py
Version
Development (host) and target OS/architectures: macOS aarch64, also seen on Linux x86_64
Output of
bazel --version
:bazel 7.2.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file:0.7.4
Language(s) and/or frameworks involved: None
How to reproduce
Any other information?
Same test passes with
rules_python
: seebazel test //runfiles_from_pipy_do_not_work:runfiles_rp_test
Exception source in runfiles.py (
rules_python
v0.34.0)The
python.runfiles
package from@rules_python//python/runfiles
works, seebazel test //runfiles_from_pipy_do_not_work:runfiles_rfrp_test //runfiles_from_pipy_do_not_work:runfiles_rp_rfrp_test
This problem was introduced in rules_py v0.7.2
The text was updated successfully, but these errors were encountered: