Sick Gaming
[Py Blog] Python 3.15.0 candidate 3 is here! - Printable Version

+- Sick Gaming (https://sickgaming.net)
+-- Forum: Programming (https://sickgaming.net/forum-76.html)
+--- Forum: Python (https://sickgaming.net/forum-83.html)
+--- Thread: [Py Blog] Python 3.15.0 candidate 3 is here! (/thread-113583.html)

[Py Blog] Python 3.15.0 candidate 3 is here! - xSicKxBot - 10-01-2026

Following
recent
tradition,
here’s a surprise third release candidate for Python 3.15.0!

We got some last-minute lazy-import release blockers, and it makes sense to
include them in 3.15.0 final. It also makes sense to give a bit of time to test
them properly, so this week’s planned 3.15.0 final is postponed until next week,
and here’s an extra 3.15.0rc3.

python.org/downloads/release/python-3150rc3

This is a candidate preview of Python 3.15

This release, 3.15.0rc3, is the final planned release candidate, containing around 156 bugfixes, build improvements and documentation changes from 82 contributors since 3.15.0rc2. Entering the release candidate phase, only reviewed code changes which are clear bug fixes are allowed between this release candidate and the final release.

The next release of Python 3.15 will be 3.15.0 final, scheduled for 2026-10-09.

There will be no ABI changes from this point forward in the 3.15 series, and the goal is that there will be as few code changes as possible.

Call to action

We strongly encourage maintainers of third-party Python projects to prepare their projects for 3.15 during this phase, and publish Python 3.15 wheels on PyPI to be ready for the final release of 3.15.0, and to help other projects do their own testing. Any binary wheels built against Python 3.15.0 release candidates will work with future versions of Python 3.15. As always, report any issues to the Python bug tracker.

Please keep in mind that this is a preview release and while it’s as close to the final release as we can get it, its use is not recommended for production environments.

Core team: extra time to work on documentation
  • Are all your changes properly documented?

  • Are they mentioned in What’s New?

  • Did you notice other changes with insufficient documentation?


Major new features of the 3.15 series, compared to 3.14

Some of the major new features and changes in Python 3.15 are:

Interpreter improvements
  • PEP 810: Explicit lazy imports for faster startup times

  • PEP 814: Add
    Code:
    frozendict
    built-in type

  • PEP 661: Add
    Code:
    sentinel
    built-in type

  • PEP 798: Unpacking in comprehensions

  • PEP 686: Python now uses UTF-8 as the default encoding

  • PEP 829: Package startup configuration files

  • The experimental JIT compiler has been significantly upgraded, with 7-8% geometric mean performance improvement on x86-64 Linux over the standard interpreter, and 11-12% speedup on AArch64 macOS over the tail-calling interpreter

  • Improved error messages


Significant improvements in the standard library
  • PEP 799: Tachyon: High frequency statistical sampling profiler

  • PEP 799: A dedicated profiling package for organizing Python profiling tools

  • More color


New typing features
  • PEP 728:
    Code:
    TypedDict
    with typed extra items

  • PEP 747: Annotating type forms with
    Code:
    TypeForm

  • PEP 800: Disjoint bases in the type system


C API improvements
  • PEP 803, 820, 793: Stable ABI for free-threaded builds and related C API

  • PEP 782: A new
    Code:
    PyBytesWriter
    C API to create a Python bytes object

  • PEP 788: Protection against finalization in the C API


Build changes
  • PEP 831: Frame pointers are enabled by default for improved system-level observability


Release changes
  • The official Windows 64-bit binaries now use the tail-calling interpreter

  • The official macOS binaries now install free-threading support by default

  • (Hey, fellow core team member, if a feature you find important is missing from this list, let Hugo know.)


For more details on the changes to Python 3.15, see What’s new in Python 3.15.

Attention macOS 27.0
Code:
IDLE
or
Code:
tkinter
users

When running IDLE or other GUI applications that use the
Code:
tkinter
module, these
applications may hang when using an application’s menu command that opens a
dialog (for example, IDLE’s
Code:
About IDLE
,
Code:
Settings
, and
Code:
Open Module
commands)
resulting in a spinning beach ball with
Code:
Force Quit
needed.

This problem is due to an operating system behavior change in macOS 27.0 that is
believed to affect all current versions of the Tk graphics toolkit and thus the
Code:
tkinter
module in all current Python versions.

If you depend on Tk-based applications (like IDLE) on macOS, you may want to
consider deferring installing macOS 27.0 until a Tk or macOS workaround is
available or testing that your application workflow is not affected. Follow
issue #158053 for updates.

More resources

And now for something completely different

Quote:At this moment the bow was in the hands of Eurymachus, who was warming
it by the fire, but even so he could not string it, and he was greatly
grieved. He heaved a deep sigh and said, “I grieve for myself and for
us all; I grieve that I shall have to forgo the marriage, but I do not
care nearly so much about this, for there are plenty of other women in
Ithaca and elsewhere; what I feel most is the fact of our being so
inferior to Ulysses in strength that we cannot string his bow. This
will disgrace us in the eyes of those who are yet unborn.”

Enjoy the new release

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.

Regards from a sunny autumnal Helsinki.

Your release team,

Hugo van Kemenade

Ned Deily

Steve Dower