Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[BUG]: nightly wheels are versioned 3.1.0 = the PyPI release since #6125, so the SPEC 4 install recipe cannot pick them up

Aperta
  • Qualcosa non va?
#6,182 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 6 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
build-system, release

Direzione di ricerca

Look at the workflow file .github/workflows/nightlies.yml and the version definitions in include/pybind11/detail/common.h. The issue is that when PYBIND11_VERSION_RELEASE_LEVEL is final, the nightly wheel uploads conflict with the PyPI release. Check how the version is set and where the upload logic decides to proceed. The fix is to either bump the version on master to an alpha (like 3.1.1a0) or modify the workflow to skip/fail on final release level. Run the reproduction commands to verify the problem.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Required prerequisites
What version (or hash if on master) of pybind11 are you using?

master 296d5d1d, as uploaded by nightly run 35680614212 (2026-09-22)

Problem description

Since #6125 set the version of record on master to 3.1.0 final (2026-08-06), the daily nightlies.yml run builds master and uploads it to scientific-python-nightly-wheels as pybind11-3.1.0-py3-none-any.whl, the same version string as the PyPI release (first such upload: run 31144654332, 2026-08-07; the 08-06 run still uploaded 3.1.0a0). Two effects, seen with pip 26.0.1:

  1. The SPEC 4 recipe the README badge points at, pip install --pre --upgrade --extra-index-url … pybind11, cannot move an environment that already has 3.1.0 onto the nightly: pip answers Requirement already satisfied: pybind11 (3.1.0).
  2. On a fresh environment, or with pybind11==3.1.0 pinned and the nightly index configured, pip picked the anaconda wheel: a master snapshot that reports __version__ == "3.1.0" and PYBIND11_VERSION_HEX == 0x030100F0. Today's upload differs from the PyPI 3.1.0 wheel in 12 header files (detail/internals.h, detail/type_caster_base.h, detail/struct_smart_holder.h, detail/init.h, pybind11.h, numpy.h, …), so a dependent testing against "the nightly" cannot tell which 3.1.0 it built against.

The upload step is green throughout ([WARNING] Distribution "pybind11-3.1.0-py3-none-any.whl" already exists. Removing. … Upload complete), so nothing flags it. After 3.0.0, #5747 bumped master to 3.0.1a0 the next day, which is what keeps a nightly sorting above the release; after 3.0.1 (f5fbe867, 2025-08-22) master stayed at 3.0.1 final until 45fab408 (2026-02-17) with this workflow running daily, so this is the second time. docs/release.rst "Post-release work" (296d5d1d, L207-209) allows "no immediate bump", and detail/common.h L24-25 says development versions use the alpha level; the nightly wheelhouse only works under the second.

Reproducible example code
$ python -m venv v && v/bin/pip -q install pybind11==3.1.0
$ v/bin/pip install --pre --upgrade --extra-index-url https://pypi.anaconda.org/scientific-python-nightly-wheels/simple pybind11
Requirement already satisfied: pybind11 in ./v/lib/python3.14/site-packages (3.1.0)

$ pip download --no-deps --pre --index-url https://pypi.anaconda.org/scientific-python-nightly-wheels/simple pybind11 -d nightly
$ pip download --no-deps pybind11==3.1.0 -d pypi
$ unzip -q nightly/*.whl -d n && unzip -q pypi/*.whl -d p && diff -rq n p | grep -vc dist-info
12
Is this a regression? Put the last known working version here if it is.

Not a regression in pybind11 itself; nightlies last sorted above the release while master was 3.1.0a0 (until run 31069110173, 2026-08-06).

Two ways to close this: bump master to 3.1.1a0 or 3.2.0a0 as #5747 did, or make nightlies.yml skip (or fail) the upload when PYBIND11_VERSION_RELEASE_LEVEL is PY_RELEASE_LEVEL_FINAL, so a nightly can never carry a published version whatever the post-release decision is. I'd take the second, since the bump alone lapsed after 3.0.1.

Found while checking the scientific-python nightly wheelhouse with Claude Code; the commands above were run as shown on 2026-09-22.

Lingua principale
C++
Stelle
18k
Fork
2.3k
Merge medio
6g 13h
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pybind/pybind11

Tutte le issue di pybind/pybind11

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.