Skip to content

Conversation

@ZeroIntensity
Copy link
Member

@ZeroIntensity ZeroIntensity commented Dec 10, 2025

Check for available Python 3.14 and Python 3.15 installations in the configure script. This allows us to use the 3.14 version installed by actions/setup-python in our 3.13 CI, rather than falling back to a 3.12 copy baked into the image.

I've omitted the blurb entry for this one, because while this is technically a change to the build, these regeneration scripts usually aren't visible in practice. If anyone is strongly in favor of adding a news entry here, feel free to let me know.

@ZeroIntensity ZeroIntensity changed the title gh-142457: Support using 3.14 and 3.15 for generation scripts [3.13] gh-142457: Support using 3.14 and 3.15 for generation scripts Dec 10, 2025
@ZeroIntensity
Copy link
Member Author

For anyone interested, the precedent here is that we check for an installed 3.15 copy in 3.14's configure script:

[python$PACKAGE_VERSION python3.15 python3.14 python3.13 python3.12 python3.11 python3.10 python3 python],

However, we don't do this for any other branches, at least as far as I can tell.

@ZeroIntensity
Copy link
Member Author

cc @hugovk

Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noting this is similar to #137619 that only backported to 3.14.

We could mark this as a backport of that, and include the NEWS. Or try a backport of that. But I don't mind much either way :)

@ZeroIntensity ZeroIntensity merged commit dc12380 into python:3.13 Dec 12, 2025
39 checks passed
@ZeroIntensity ZeroIntensity deleted the 3.13-new-versions-ci branch December 12, 2025 18:09
@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Arch Linux TraceRefs 3.13 (no tier) has failed when building commit dc12380.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1472/builds/897) and take a look at the build logs.
  4. Check if the failure is related to this commit (dc12380) or if it is a false positive.
  5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1472/builds/897

Failed tests:

  • test_urllib2net

Summary of the results of the build (if available):

==

Click to see traceback logs
remote: Enumerating objects: 4, done.        
remote: Counting objects:  50% (1/2)        
remote: Counting objects: 100% (2/2)        
remote: Counting objects: 100% (2/2), done.        
remote: Compressing objects:  50% (1/2)        
remote: Compressing objects: 100% (2/2)        
remote: Compressing objects: 100% (2/2), done.        
remote: Total 4 (delta 1), reused 0 (delta 0), pack-reused 2 (from 1)        
From https://github.com/python/cpython
 * branch                    3.13       -> FETCH_HEAD
Note: switching to 'dc12380f600d82343edd6d6bfb2375568db96f26'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at dc12380f600 [3.13] gh-142457: Support using 3.14 and 3.15 for generation scripts (GH-142499)
Switched to and reset branch '3.13'

make: *** [Makefile:2252: buildbottest] Error 2

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants