Error computing the main repository mapping: no such package '@pip_deps//
🐞 bug report
Description
A clear and concise description of the problem...I'm trying to build projects that seem to reference the usage of pip_deps. I'm not 100% sure if this is the right repo for this, but every time, it seems like I get the following error message:
Unable to find package for @pip_deps//:requirements.bzl: The repository '@pip_deps' could not be resolved: Repository '@pip_deps' is not defined. and referenced by '//main:main'
ERROR: Analysis of target '//main:main' failed; build aborted: Analysis failed
INFO: Elapsed time: 0.134s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 0 targets configured)
currently loading: @pytorch// ... (2 packages)
Fetching repository @rules_cuda; starting
Fetching repository @pybind11_bazel; starting
Does pip_deps belong here?
🔬 Minimal Reproduction
In the torch BUILD file: https://github.com/pytorch/pytorch/blob/v2.1.1-rc4/WORKSPACE#L214-L222
🌍 Your Environment
Operating System: Mac OS Ventura 13.6
Output of bazel version:
Bazelisk version: development
Build label: 6.4.0
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Oct 19 17:15:28 2023 (1697735728)
Build timestamp: 1697735728
Build timestamp as int: 1697735728
Rules_python version: 0.26.0
Anything else relevant?
It is hard to understand what kind of setup you have to help you. Could you paste a minimal example that reproduces the error in addition to the source of the error please?
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!
This issue was automatically closed because it went 30 days without a reply since it was labeled "Can Close?"