go:embed stdlib_list.txt file in gazelle/python/std_modules.go is missing
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- build-system
Research direction
Start with gazelle/python/std_modules.go and inspect the go:embed reference to stdlib_list.txt. Reproduce the failure with go list -deps ./... using the reported Gazelle dependency, then verify the missing embedded file is present and the command completes successfully.
Written by the indexing model from the issue text.
Description
🐞 bug report
Affected Rule
The issue is caused by the rule:Is this a regression?
Yes, the previous version in which this bug was not present was: ....Description
A clear and concise description of the problem...Adding Gazelle to go.mod results in a failure running go list -deps ./... because the stdlib_list.txt used in the go:embed in gazelle/python/std_modules.go does not exist
🔬 Minimal Reproduction
Add something like the following to go.mod
github.com/bazel-contrib/rules_python/gazelle v0.0.0-20260330223627-293e643aa3ea
go list -deps ./... > /dev/null
🔥 Exception or Error
../../pkg/mod/github.com/bazel-contrib/rules_python/gazelle@v0.0.0-20260330223627-293e643aa3ea/python/std_modules.go:24:13: pattern stdlib_list.txt: no matching files found
🌍 Your Environment
Operating System:
macOS 15.4.1
Output of bazel version:
$ bazel version
Build label: 7.7.1
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Wed Nov 12 17:35:45 2025 (1762968945)
Build timestamp: 1762968945
Build timestamp as int: 1762968945
Rules_python version:
1.8.4
Anything else relevant?
- Dominant language
- Starlark
- Stars
- 690
- Forks
- 722
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 50
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bazel-contrib/rules_python
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bazel-contrib/rules_python#4164 · 1 comment ·
-
Release 2.4.0 Opentype: release
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bazel-contrib/rules_python#4175 ·
-
Release 2.3.4 Opentype: release
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
bazel-contrib/rules_python#4173 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
bazel-contrib/rules_python#4171 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
bazel-contrib/rules_python#4168 ·
All issues in bazel-contrib/rules_python
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
Builders
Difficulty 2/5 1-3 hours Newbie friendliness 72/100