[3.13] gh-141004: Add a CI job ensuring that new C APIs include documentation (GH-142102)#142248
Conversation
…ntation (pythonGH-142102) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> (cherry picked from commit 1a7824a)
… documentation (pythonGH-142102) (cherry picked from commit 1a7824a) Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
@hugovk Quick question -- it seems CI on 3.13 uses Python 3.12, not 3.13. Is that intentional? If so, I need to remove the use of |
Sorry, something went wrong.
|
Hmm, well we're installing However, for the 3.14 branch, when we run But on this 3.13 branch, for some reason we get: I'm not sure why configure is selecting 3.12... |
Sorry, something went wrong.
|
Do you know if the configure script on 3.13 checks for 3.14? I think that might be the problem. I'm guessing that Python 3.12 is already installed on the system the CI job is running on, and |
Sorry, something went wrong.
No, it only checks the current version and lower.
Line 3828 in 756e7d1
Line 3820 in f200776
Line 3765 in b57d695
Yes, that indeed looks like the problem. Here's a test workflow that installs a give version, then tries to check for them all: python3.15 --version --version || true
python3.14 --version --version || true
python3.13 --version --version || true
python3.12 --version --version || true
python3.11 --version --version || true
python3.10 --version --version || trueAnd they all have the given version, plus 3.12. For example with 3.15: And it's an old 3.12.3 baked into the image, because when we specifically ask for 3.12 we get the newest 3.12.12: |
Sorry, something went wrong.
5569ffe
into
python:3.13
Dec 15, 2025
(cherry picked from commit 1a7824a)