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
pip_repository should always write a requirements.bzl file. Printing the contents should be a sideeffect.
🔬 Minimal Reproduction
From the root of rules_python:
cd examples/pip_parse &&export BUILD_WORKING_DIRECTORY=$(pwd)&& bazel test //...
🔥 Exception or Error
pip_parse % bazel test //...
Starting local Bazel server and connecting to it...
INFO: Invocation ID: 9b05ae6c-b5e9-42f6-9820-376b018e7233
ERROR: error loading package '': cannot load '@pypi//:requirements.bzl': no such file
INFO: Elapsed time: 6.276s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)
I also hit this error specifically when switching between branches that had different requirements. We resolved this by downgrading to rules_python 0.7.0, but hopefully a fix for this will make it into the next release.
Activity
UebelAndre commentedon Mar 31, 2022
cc @alexeagle
rahul-theorem commentedon Apr 19, 2022
I also hit this error specifically when switching between branches that had different requirements. We resolved this by downgrading to rules_python 0.7.0, but hopefully a fix for this will make it into the next release.
alexeagle commentedon Apr 20, 2022
Sorry about that, I'm trying to fix in #679 but got stuck there