# Python 3.12.7 and 3.13.0rc3 released

**URL:** <https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306>\
**Category:** Core Development\
**Tags:** release\
**Created:** [October 1, 2024, 2:48pm UTC](https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306 "2024-10-01T14:48:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomas](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/thomas/32/5492_2.png) [@thomas](https://discuss.python.org/u/thomas)\
**Post date:** [October 1, 2024, 2:48pm UTC](https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306/1 "2024-10-01T14:48:30Z")

</div>

## This is not the release you’re looking for…

(unless you’re looking for 3.12.7.)

Because no plan survives contact with reality, instead of the actual Python 3.13.0 release we have a new **Python 3.13 release candidate** today. Python 3.13.0rc3 rolls back the incremental cyclic garbage collector (GC), which was added in one of the alpha releases. The incremental GC had more significant performance regressions in specific workloads than we expected. Rather than try to fiddle with its details in the hope of fixing them (and not making anything else worse) we decided to revert back to the old GC in 3.13. Work on the incremental GC will continue in 3.14. We also took the opportunity to fix some other (rare) bugs and issues found in 3.13.0rc2. **The final release of Python 3.13.0 will now happen next week** , **Monday October 7th**.

In an effort to return to normalcy, we’ve also released Python 3.12.7 as scheduled, despite the expedited release a month ago. It’s important to be regular!

## 3.13.0rc3

> **[Python Release Python 3.13.0rc3](https://www.python.org/downloads/release/python-3130rc3/)**
>
> The official home of the Python Programming Language

The final cut of 3.13.0 (really, honest). Besides the incremental GC revert it contains a small number of other fixes, as well as many documentation improvements and testsuite improvements (~145 changes in total).

#### Call to action

We strongly encourage maintainers of third-party Python projects to prepare their projects for 3.13 compatibilities during this phase, and where necessary publish Python 3.13 wheels on PyPI to be ready for the final release of 3.13.0. Any binary wheels built against Python 3.13.0rc1 and later will work with future versions of Python 3.13. As always, report any issues to [the Python bug tracker](https://github.com/python/cpython/issues).

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. Next week, though!

#### New features in Python 3.13

- A [new and improved interactive interpreter](https://docs.python.org/3.13/whatsnew/3.13.html#a-better-interactive-interpreter), based on [PyPy](https://pypy.org)’s, featuring multi-line editing and color support, as well as colorized [exception tracebacks](https://docs.python.org/3.13/whatsnew/3.13.html#improved-error-messages).
- An [_experimental_ free-threaded build mode](https://docs.python.org/3.13/whatsnew/3.13.html#free-threaded-cpython), which disables the Global Interpreter Lock, allowing threads to run more concurrently. The build mode is available as an experimental feature in the Windows and macOS installers as well.
- A [preliminary, _experimental_ JIT](https://docs.python.org/3.13/whatsnew/3.13.html#experimental-jit-compiler), providing the ground work for significant performance improvements.
- The `locals()` builtin function (and its C equivalent) now has [well-defined semantics when mutating the returned mapping](https://docs.python.org/3.13/whatsnew/3.13.html#defined-mutation-semantics-for-locals), which allows debuggers to operate more consistently.
- A modified version of [mimalloc](https://github.com/microsoft/mimalloc) is now included, optional but enabled by default if supported by the platform, and required for the free-threaded build mode.
- Docstrings now have [their leading indentation stripped](https://docs.python.org/3.13/whatsnew/3.13.html#other-language-changes), reducing memory use and the size of .pyc files. (Most tools handling docstrings already strip leading indentation.)
- The [dbm module](https://docs.python.org/3.13/library/dbm.html) has a new [dbm.sqlite3 backend](https://docs.python.org/3.13/whatsnew/3.13.html#dbm) that is used by default when creating new files.
- The minimum supported macOS version was changed from 10.9 to **10.13 (High Sierra)**. Older macOS versions will not be supported going forward.
- WASI is now a [Tier 2 supported platform](https://peps.python.org/pep-0011/#tier-2). Emscripten is no longer an [officially supported platform](https://peps.python.org/pep-0011/#no-longer-supported-platforms) (but [Pyodide](https://pyodide.org) continues to support Emscripten).
- iOS is now a [Tier 3 supported platform](https://peps.python.org/pep-0730/).
- Android is now a [Tier 3 supported platform](https://peps.python.org/pep-0738/) as well.

## Python 3.12.7

> **[Python Release Python 3.12.7](https://www.python.org/downloads/release/python-3127/)**
>
> The official home of the Python Programming Language

A small release since 3.12.6 was only a month ago, but nevertheless 3.12.7 contains ~120 bug fixes, build improvements and documentation changes.

## More resources

- [Python 3.13 Online Documentation](https://docs.python.org/3.13/)
- [PEP 719](https://peps.python.org/pep-0719/), Python 3.13 Release Schedule
- Report bugs at [Issues · python/cpython · GitHub](https://github.com/python/cpython/issues).
- [Help fund Python directly](https://www.python.org/psf/donations/python-dev/) (or [via GitHub Sponsors](https://github.com/sponsors/python)), and support [the Python community](https://www.python.org/psf/donations/).

## 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 organization contributions to the Python Software Foundation.

Regards from a positively _melting_ [Menlo Park for some reason](https://social.coop/@Yhg1s/113051321976759729) this time,

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

---

<div class="post-metadata">

**Author:** ![mgorny](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/mgorny/32/34029_2.png) [@mgorny](https://discuss.python.org/u/mgorny)\
**Post date:** [October 1, 2024, 7:24pm UTC](https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306/2 "2024-10-01T19:24:17Z")

</div>

Is it intentional that `python-3.12.7-docs-html.tar.bz2` has the directory named `python-3.12-docs-html` rather than `python-3.12.7-docs-html`, as have been in the previous releases?

---

<div class="post-metadata">

**Author:** ![Jelle](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jelle/32/1049_2.png) [@Jelle](https://discuss.python.org/u/Jelle)\
**Post date:** [October 1, 2024, 7:50pm UTC](https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306/3 "2024-10-01T19:50:28Z")

</div>

This was an accident. We got a fix in [Doc: Fix archive filenames for standard builds by AA-Turner · Pull Request #124826 · python/cpython · GitHub](https://github.com/python/cpython/pull/124826) but I believe Thomas made some manual fixes for today’s two releases. I expect future releases will go back to the previous pattern.

---

<div class="post-metadata">

**Author:** ![jcea](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jcea/32/22932_2.png) [@jcea](https://discuss.python.org/u/jcea)\
**Post date:** [October 4, 2024, 3:49am UTC](https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306/4 "2024-10-04T03:49:58Z")

</div>

1. In [https://www.python.org/](https://www.python.org/) → Downloads, the current stable release is listed as 3.12.6 (not 3.12.7).
2. [Python Release Python 3.12.7 | Python.org](https://www.python.org/downloads/release/python-3127/) page shows no changelog for 3.12.7, so regular people don’t know what has been changed.

Thanks.

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [October 4, 2024, 5:52am UTC](https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306/5 "2024-10-04T05:52:02Z")

</div>

> [@jcea](#):
>
> 1. In [https://www.python.org/](https://www.python.org/) → Downloads, the current stable release is listed as 3.12.6 (not 3.12.7).

Hmm, the “Downloads” tab at [https://www.python.org/](https://www.python.org/) has a 3.12.6 download button (on macOS), and the “Download” box links to 3.12.6. However, [https://www.python.org/downloads/](https://www.python.org/downloads/) has the correct download button for 3.12.7…

Let’s ask @JacobCoffee.

> [@jcea](#):
>
> 1. [Python Release Python 3.12.7 | Python.org](https://www.python.org/downloads/release/python-3127/) page shows no changelog for 3.12.7, so regular people don’t know what has been changed.

I’ve updated it to include a link to the full changelog: [Changelog — Python 3.12.7 documentation](https://docs.python.org/release/3.12.7/whatsnew/changelog.html#python-3-12-7)

---

<div class="post-metadata">

**Author:** ![JacobCoffee](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jacobcoffee/32/36007_2.png) [@JacobCoffee](https://discuss.python.org/u/JacobCoffee)\
**Post date:** [October 4, 2024, 5:53am UTC](https://discuss.python.org/t/python-3-12-7-and-3-13-0rc3-released/66306/6 "2024-10-04T05:53:26Z")

</div>

We nightowls were looking a bit ago but I’ll dig in in the morning

> <https://github.com/python/pythondotorg/issues/2631>
>
> \### Describe the bug
> 
> With Python 3.12.7 released on 2 Oct 2024, the latest ve…rsion listed in the Download block on the main page still lists 3.12.6. Also, the Downloads popup in the site navigation also references 3.12.6.
> 
> \### To Reproduce
> 
> Downloads navigation popup
> 
> 1. Open a web browser
> 2. Browse to \<https://www.python.org\>
> 3. Hover cursor over the \*\*Downloads\*\* navigation item
> 
> Downloads Latest
> 
> 1. Open a web browser
> 2. Browse to \<https://www.python.org\>
> 3. Scroll down to the \*\*Get Started\*\* and \*\*Downloads\*\* blocks, Latests lists the previous version
> 
> \### Expected behavior
> 
> In both locations, 3.12.7 should be listed as the latest version and should link to the appropriate \[release page\](https://www.python.org/downloads/release/python-3127/) or to the appropriate \[release tarball\](https://www.python.org/ftp/python/3.12.7/Python-3.12.7.tar.xz)
> 
> \### URL to the issue
> 
> https://www.python.org/
> 
> \### Screenshots
> 
> !\[image\](https://github.com/user-attachments/assets/224d68ea-5fd3-40c9-862a-14b2e72fdd25)
> 
> !\[image\](https://github.com/user-attachments/assets/fa2842f7-c57f-4991-84db-2c6aadb01019)
> 
> 
> \### Browsers
> 
> Firefox, Chrome
> 
> \### Operating System
> 
> Linux
> 
> \### Browser Version
> 
> 130
> 
> \### Relevant log output
> 
> \_No response\_
> 
> \### Additional context
> 
> \_No response\_

edit: all fixed up 🙂
