Skip to content

docs: add a supported versions page - #6279

Open
henryiii wants to merge 4 commits into
pybind:masterfrom
henryiii:docs/supported-versions
Open

henryiii wants to merge 4 commits into
pybind:masterfrom
henryiii:docs/supported-versions

Conversation

@henryiii

@henryiii henryiii commented Nov 15, 2026 •

Copy link
Copy Markdown
Collaborator

🤖 AI text below 🤖

Description

Add a "Supported versions" page with one table for the minimum versions of Python implementations, compilers, C++ standard, CMake, and optional dependencies. Each row has two values:

  • Minimum expected: the oldest version we intend to work (mostly from the #error checks in common.h, CMake, and the changelog).
  • Minimum tested: the oldest version in the CI matrix.

The README links to the page, and AGENTS.md asks agents to update it when a minimum changes.

Open questions: there is no stated minimum for GraalPy, NVCC, NVHPC, or NumPy. Also, the GCC 4.8 / Clang 3.3 header checks are likely older than what works today.

Suggested changelog entry:

  • Added a docs page that lists the minimum expected and minimum tested versions of supported tools and dependencies.

📚 Documentation preview 📚: https://pybind11--6279.org.readthedocs.build/

List the minimum expected and minimum tested version of each Python
implementation, compiler, and dependency.

Assisted-by: ClaudeCode:claude-opus-5-5
Assisted-by: ClaudeCode:claude-opus-5-5
Assisted-by: ClaudeCode:claude-opus-5-5
@henryiii
henryiii marked this pull request as ready for review November 16, 2026 03:37
@rwgk

rwgk commented Nov 21, 2026

Copy link
Copy Markdown
Collaborator

— codex on behalf of Ralf —

Align the support table with the README. The new table lists GraalPy 25.0 as both the minimum expected and the minimum tested version, while the README still lists GraalPy 24.1+. Is 25.0 an intentional change to what users should expect to work? If the change is to test coverage, the two columns can reflect that distinction. The expected PyPy row could also cite the README’s specific PyPy3 7.3.17+ minimum alongside the Python compatibility version. New support table · README support statement

Generated by Codex. Ralf has yet to review these findings.

Assisted-by: ClaudeCode:claude-fable-5-2
@henryiii

Copy link
Copy Markdown
Collaborator Author

🤖 AI text below 🤖

Changes are in a653115.

  • GraalPy: CI tests graalpy-25.0 and graalpy-25.3 only. CI moved from 24.2 to 25.0 in ci: update GraalPy from 24.2 to 25.0 (Python 3.12 based) #6083 (first release: 3.1.0). I changed the README to "GraalPy 25.0+", so the README and the table agree with CI. The table note now says that CI tested 24.x before pybind11 3.1 and that we do not test it now. This raises the stated minimum, so @henryiii must confirm it. The alternative is to keep 24.1 in the README and in the "minimum expected" column, with 25.0 as "minimum tested". The header fallback for GraalPy older than 25.0 (def_submodule in pybind11-inl.h) is still there.
  • PyPy: The "minimum expected" cell now says "3.10 (v7.3.17)", the same as the README. The "minimum tested" value (3.11, v7.3.23) agrees with ci.yml.

@henryiii

Copy link
Copy Markdown
Collaborator Author

I think 25.0+ is fine for GraalPy.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants