bazel-contrib / bazel-contrib/rules_python

py_cc_toolchain should contain EXT_SUFFIX

Offen
#2,870 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Starlark
Sterne
688
Forks
721
Ø Merge
15 Std. 7 Min.
Gemergte PRs (30 T.)
76

Beschreibung

See https://github.com/bazelbuild/bazel-central-registry/pull/4539#discussion_r2080143661 for some context.

This value is needed to create python extensions. Note that there are a few different names that can be used, for example `.so`, `.abi3.so`, and `.cpython-312-x86_64-linux-gnu.so`. The latter is preferable when not using the python limited api because it prevents runfiles conflicts between python versions properly, meaning that transitions can work without completely breaking things.

I believe for autoconfigured pythons, you could obtain this value like so:

```
❯ python -c 'import sysconfig; print(sysconfig.get_config_var("EXT_SUFFIX"))'
.cpython-312-x86_64-linux-gnu.so
```

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start with the py_cc_toolchain autoconfiguration path and review the linked bazel-central-registry discussion for context. Run the shown Python sysconfig command to inspect EXT_SUFFIX values; done means the toolchain exposes the appropriate suffix, including the full interpreter-specific form when available.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python
Bereich
build-system
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.