Skip to content

Conversation

@rwgk
Copy link
Collaborator

@rwgk rwgk commented Nov 29, 2025

  • Replace the hard-coded “Supported compilers” and “Supported platforms” lists in README.rst.

  • Point readers to the current GitHub Actions matrix as the source of truth for tested platforms, compilers, and Python/C++ versions.

  • Clarify that the matrix evolves over time and that configurations users care about can be kept working via contributions.

  • Avoid stale documentation: Enumerating specific compiler and platform versions in the README is both burdensome and error-prone, and tends to drift out of sync with reality.

  • Align “supported” with “tested”: In practice, the CI configuration is the only place where we can say with confidence which combinations are exercised. Nearby versions (e.g., adjacent compiler minor releases) will often work, but we cannot test every variant.

  • Reflect actual maintenance capacity: pybind11 is maintained by a small, volunteer-based community, so support is necessarily best-effort. Pointing to CI and inviting contributions better matches how support is provided in practice.

  • No behavior change: This PR updates documentation only.

  • Living source of truth: As CI jobs are added or removed, the linked Actions view will automatically reflect the set of configurations we actively test. Keeping a configuration in CI is the best way to keep it “supported”.

Description

Suggested changelog entry:

  • The “Supported compilers” and “Supported platforms” sections in the main README.rst were replaced with a new “Supported platforms & compilers“ section that points to the CI test matrix as the living source of truth.

…pilers

- **Replace** the hard-coded “Supported compilers” and “Supported platforms” lists in `README.rst`.
- **Point** readers to the current GitHub Actions matrix as the source of truth for tested platforms, compilers, and Python/C++ versions.
- **Clarify** that the matrix evolves over time and that configurations users care about can be kept working via contributions.

- **Avoid stale documentation**: Enumerating specific compiler and platform versions in the README is both burdensome and error-prone, and tends to drift out of sync with reality.
- **Align “supported” with “tested”**: In practice, the CI configuration is the only place where we can say with confidence which combinations are exercised. Nearby versions (e.g., adjacent compiler minor releases) will often work, but we cannot test every variant.
- **Reflect actual maintenance capacity**: pybind11 is maintained by a small, volunteer-based community, so support is necessarily best-effort. Pointing to CI and inviting contributions better matches how support is provided in practice.

- **No behavior change**: This PR updates documentation only.
- **Living source of truth**: As CI jobs are added or removed, the linked Actions view will automatically reflect the set of configurations we actively test. Keeping a configuration in CI is the best way to keep it “supported”.
@rwgk rwgk requested a review from henryiii November 29, 2025 05:53
@rwgk rwgk mentioned this pull request Nov 29, 2025
3 tasks
@rwgk
Copy link
Collaborator Author

rwgk commented Nov 29, 2025

Thanks @Skylion007 for this one, too!

@rwgk rwgk merged commit 734c29b into pybind:master Nov 29, 2025
3 checks passed
@rwgk rwgk deleted the readme_supported_compilers_update branch November 29, 2025 21:16
@github-actions github-actions bot added the needs changelog Possibly needs a changelog entry label Nov 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs changelog Possibly needs a changelog entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants