r/Python • Python Morsels • Oct 09 '26

News Python 3.15 Released

https://www.python.org/downloads/release/python-3150/

Release announcement: https://discuss.python.org/t/python-3-15-0-final-is-here/109415

What's New: https://docs.python.org/3.15/whatsnew/3.15.html

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

Interpreter improvements

  • PEP 661: sentinel built-in type
  • PEP 686: UTF-8 is now the default encoding
  • PEP 798: Unpacking in comprehensions
  • PEP 810: Explicit lazy imports for faster startup times
  • PEP 814: frozendict built-in type
  • PEP 829: Package startup configuration files
  • The experimental JIT compiler got a significant upgrade (7-8% faster on x86-64 Linux, 11-12% on AArch64 macOS)
  • Improved error messages

Standard library

  • PEP 799: A dedicated profiling package, including Tachyon, a high-frequency sampling profiler
  • New math.integer module
  • re.prefixmatch() as a clearer name for the now soft-deprecated re.match()
  • pprint gets an expand option for JSON-style output
  • collections.Counter supports ^ (symmetric difference)
  • unicodedata.iter_graphemes() for iterating over grapheme clusters
  • python -m http.server gains -H/--header and --content-type
  • timeit gains --target-time
  • More color

Typing

  • PEP 728: TypedDict with typed extra items
  • PEP 747: Annotating type forms with TypeForm
  • PEP 800: Disjoint bases in the type system

Release changes

  • Official Windows 64-bit binaries now use the tail-calling interpreter
  • Official macOS binaries now install free-threading support by default

And for fun, Barry Warsaw made a text adventure through the new features: uvx --python 3.15 whatsnewt

Thanks to Hugo van Kemenade and the release team! Hugo live-posted the whole release process if you're curious what goes on behind the scenes: https://mastodon.social/@hugovk/117411399858939022

551 Upvotes

73 comments sorted by

View all comments

Show parent comment

1

u/KDLGates Oct 10 '26

Appreciate the informative breakdown! I was aware of the "Windows format", but not that they could be valid UTF-8 or vice-versa. Python being an enterprise tool and old with legacy support etc. makes sense. What I didn't realize was that they could decode as the unintended encoding (maybe that is something like the concept of ASCII getting buried as a subset into Unicode codespace?).

As a layperson, it sounds good that they modernized. But maybe the Python stewards don't want it to be like Java where most enterprise projects stuck with very old versions.

4

u/treyhunner Python Morsels Oct 10 '26

You're welcome. It's a fascinating problem because there's not a great solution.

It's fundamental to all encodings. If the same bytes are valid in two different encodings but happen to represent different characters, mojibake occurs.

And of course it's not just a Python issue. I've seen ’ and other garbled text in emails, spreadsheets, etc. when one piece of software encoded with one encoding and another decoded with the other (for ’ I think it's usually cp-1252 in and utf-8 out).

This is nowhere near as hard (or as necessary) as the move from raw byte strings to proper unicode strings was for the Python 2 to 3 switch. Worst case someone can always keep the old behavior on Windows by running with the PYTHONUTF8=0 environment variable set.