Python 3.15.0a8, 3.14.4 and 3.13.13 are now available! (original) (raw)

Another day month, another set of releases!

Python 3.15.0 alpha 8

This is an early developer preview of Python 3.15

Major new features of the 3.15 series, compared to 3.14

Python 3.15 is still in development. This release, 3.15.0a8, is the final planned alpha release.

Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process.

During the alpha phase, features may be added up until the start of the beta phase (2026-05-05) and, if necessary, may be modified or deleted up until the release candidate phase (2026-07-28). Please keep in mind that this is a preview release and its use is not recommended for production environments.

Many new features for Python 3.15 are still being planned and written. Among the new major new features and changes so far:

• PEP 810: Explicit lazy imports
• PEP 814: frozendict built-in type
• PEP 799: A new high-frequency, low-overhead, statistical sampling profiler and dedicated profiling package
• PEP 798: Unpacking in comprehensions with * and **
• PEP 686: Python now uses UTF-8 as the default encoding
• PEP 728: TypedDict with typed extra items
• PEP 747: Annotating type forms with TypeForm
• PEP 782: A new PyBytesWriter C API to create a Python bytes object
• The JIT compiler has been significantly upgraded, with 6-7% geometric mean performance improvement on x86-64 Linux over the standard interpreter, and 12-13% speedup on AArch64 macOS over the tail-calling interpreter
• The official Windows 64-bit binaries now use the tail-calling interpreter
• Improved error messages
• (Hey, fellow core team member, if a feature you find important is missing from this list, let Hugo know.)

The next pre-release of Python 3.15 will be 3.15.0b1, scheduled for 2026-05-05.

More resources

• Online documentation
• PEP 790, 3.15 release schedule
• Report bugs at https://github.com/python/cpython/issues
• Help fund Python directly (or via GitHub Sponsors) and support the Python community

Python 3.14.4

Python 3.14.4 is the fourth maintenance release of 3.14, containing around 337 bugfixes, build improvements and documentation changes since 3.14.3.

Python 3.13.13

Python 3.13.13 is the lucky thirteenth maintenance release of 3.13, containing around 200 bugfixes, build improvements and documentation changes since 3.13.12.

Enjoy the new releases

Thanks to all of the many volunteers who help make Python development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the Python Software Foundation.

Your release team,
Hugo van Kemenade @hugovk
Thomas Wouters @thomas
Ned Deily @nad
Steve Dower @steve.dower
Łukasz Langa @ambv

And to save @barry some typing since he’s busy with his PEP, the container images were (most likely) updated automatically.

barry (Barry Warsaw) April 8, 2026, 2:09am 3

Ha, I’ll show you!

The GitLab build pipeline runs nightly at 00:17 UTC, so they should show up tomorrow.

hugovk (Hugo van Kemenade) April 8, 2026, 4:35am 4

I regret to inform you that if it had run at 00:17 UTC, it would have picked them up. But 0 17 * * * Etc/UTC is 17:00 UTC (and it actually ran at 17:45 UTC).

mcepl (Matěj Cepl) April 8, 2026, 8:29am 5

hugovk (Hugo van Kemenade) April 8, 2026, 9:24am 6

That’s intentional:

gh-148197 (added docs and) reverted gh-146122, including the changelog entry because it hadn’t been released yet.

And we have disputed CVE-2026-3479:

DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security model. pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.

vstinner (Victor Stinner) April 8, 2026, 9:29am 7

I’m not sure what you means by “duplicate” here. The issue gh-144741 is about a failure of test_frame_pointer_unwind. And test_frame_pointer_unwind was added by issue gh-126910.

barry (Barry Warsaw) April 8, 2026, 9:14pm 8

Yep, oops! I got discronbobulated. In fact the new versions didn’t get picked up until 4 hours ago, so I think I’ll push that back to actually ~midnight UTC.