Bazel fetches the rules_python repository from somewhere without having a definition of this repository in the project
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
### Description of the bug:
rules_python doesn't have any kind of definition in my project, like http_archive or git_repository definitions, but bazel still fetches it from somewhere.
It looks like the rules_python repository definition is leaked from the bazel build itself, because it is defined in bazel's sourcecode.
In fact, defining rules_python like this doesn't make a difference:
```
http_archive(
name = "rules_python",
sha256 = "c68bdc4fbec25de5b5493b8819cfc877c4ea299c0dcb15c244c5a00208cde311",
strip_prefix = "rules_python-0.31.0",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.31.0/rules_python-0.31.0.tar.gz",
)
```
bazel still uses the same version of rules_python that it uses without such repository definition.
### Which category does this issue belong to?
_No response_
### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
_No response_
### Which operating system are you running Bazel on?
_No response_
### What is the output of `bazel info release`?
_No response_
### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.
_No response_
### What's the output of `git remote get-url origin; git rev-parse HEAD` ?
```text
```
### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
_No response_
Contributor guide
Research direction
The report names no source files, tests, or reproducible command. First obtain a minimal Bazel workspace, the exact fetch output, Bazel release, operating system, and repository commit; then trace which Bazel-built definition supplies rules_python. Done means reproducing the unexpected fetch and identifying a concrete regression or correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100