py_proto_library rule not using prebuilt protoc
I maintainer di solito rispondono entro 1 giorno
@anandolee ci sta già lavorando.
Dal 16/6/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
What version of protobuf and what language are you using?
Version: 35.1
Language: Python
What supported operating system version are you using (e.g. Linux, Windows) ?
macOS 26.5.1
What supported runtime / compiler version are you using (e.g. python version, gcc version)
Bazel 9.1.0
rules_python 2.0.0
Python 3.13 toolchain from rules_python
What did you do?
I have what I think is a pretty vanilla Bazel/Python/Protobuf configuration, and I'm trying to use the recently-released support for prebuilt protobuf compiler binaries. It's not working - trying to build a py_proto_library rule results in the protobuf compiler being built from source.
To debug, I ran bazel cquery 'somepath("//my_project/proto:my_py_proto", "@protobuf//src/google/protobuf")' which gave me the following dependency chain:
//my_project/proto:my_py_proto
@protobuf//python:python_toolchain
@protobuf//python:protobuf_python
@protobuf//python:python_srcs
@protobuf//python:python_src_files
@protobuf//python:google/protobuf/internal/python_edition_defaults.py
@protobuf//python:embedded_python_edition_defaults_generate
@protobuf//editions:internal_defaults_escape
@protobuf//src/google/protobuf:protobuf
My uneducated guess at narrowing down the problem is that @protobuf//python:python_toolchain is mis-resolving such that it depends on @protobuf//python:protobuf_python, which in turn depends on python_edition_defaults.py, in turn generated from C++ stuff. I would expect the dependency chain to stop after python_toolchain. To the extent that Python sources are needed to compile my protos, I'd expect them to be part of the prebuilt compiler distribution, and to the extent they're needed at runtime I'd expect to get them from PyPI. But my convictions aren't very strong here, maybe I'm doing something obviously wrong?
For good measure I also tried
bazel build //my_project/proto:my_py_proto \
--'@protobuf//bazel/flags:prefer_prebuilt_protoc' \
--incompatible_enable_proto_toolchain_resolution
with the same result.
What did you expect to see
Prebuilt compiler used, compiler not built from source
What did you see instead?
Compiler built from source
Anything else we should know about your project / environment
I have some gross workarounds in my BUILD files to relocate the proto Python modules going into the wheel I'm trying to build, but all of that is downstream of the py_proto_library rule and I wouldn't expect it to affect the proto library's upstream dependencies.
- Lingua principale
- C++
- Stelle
- 72.2k
- Fork
- 16.4k
- Merge medio
- 1g 8h
- PR unite (30g)
- 342
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di protocolbuffers/protobuf
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
protocolbuffers/protobuf#31768 ·
I maintainer di solito rispondono entro 1 giorno
-
feature request packaging & distribution python
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
protocolbuffers/protobuf#31654 ·
I maintainer di solito rispondono entro 1 giorno
-
google-protobuf 0.36.2-release fails to compile for ARMv7: @progbits rejected in global_asm!Forse già presa @farisbasha l’ha presa 2 giorni fa. Apertabug help wanted rust
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
protocolbuffers/protobuf#31619 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Null pointer passed to memcpy in lupb_decode() when the second argument is nilForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug help wanted lua
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
protocolbuffers/protobuf#31392 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
upb: JSON encoder does not range-check Duration and Timestamp nanos (signed overflow on -2^31)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
protocolbuffers/protobuf#31032 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di protocolbuffers/protobuf
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 7 giorni
-
bug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
microsoft/DirectXShaderCompiler#9155 ·
I maintainer di solito rispondono entro 2 giorni
-
Errors in 1.20 proseApertaCampaign DiD Campaign EI Campaign HttT Campaign TDG Campaign TSG Campaign WoF Enhancement Help Prose Stable 1.20
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
wesnoth/wesnoth#11749 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno