# Python 3.13.0RC2, 3.12.6, 3.11.10, 3.10.15, 3.9.20, and 3.8.20 are now available! **URL:** \ **Category:** Core Development\ **Tags:** release\ **Created:** [September 7, 2024, 9:57am UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161 "2024-09-07T09:57:15Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\ **Post date:** [September 7, 2024, 9:57am UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/1 "2024-09-07T09:57:15Z")
Hi there! A big joint release today. Mostly security fixes but we also have the final release candidate of 3.13 so let’s start with that! ## Python 3.13.0RC2 Final opportunity to test and find any show-stopper bugs before we bless and release 3.13.0 final on October 1st. Get it here: > **[Python Release Python 3.13.0rc2](https://www.python.org/downloads/release/python-3130rc2/)** > > The official home of the Python Programming Language #### 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.0rc2 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. #### Core developers: time to work on documentation now - Are all your changes properly documented? - Are they mentioned in [What’s New](https://docs.python.org/3.13/whatsnew/3.13.html)? - Did you notice other changes you know of to have insufficient documentation? As a reminder, until the final release of 3.13.0, the 3.13 branch is set up so that the Release Manager (@thomas) has to merge the changes. Please add him (`@Yhg1s` on GitHub) to any changes you think should go into 3.13.0. At this point, unless something critical comes up, it should really be **documentation only**. Other changes (including tests) will be pushed to 3.13.1. #### 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. - The (cyclic) garbage collector is now [incremental](https://docs.python.org/3.13/whatsnew/3.13.html#incremental-garbage-collection), which should mean shorter pauses for collection in programs with a lot of objects. - 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/), with [Android on the way as well](https://peps.python.org/pep-0738/). ## Python 3.12.6 This is an expedited release for 3.12 due to security content. The schedule returns back to regular programming in October. One notable change for macOS users: as mentioned in the previous release of 3.12, this release **drops support for macOS versions 10.9 through 10.12**. Versions of macOS older than 10.13 haven’t been supported by Apple since 2019, and maintaining support for them has become too difficult. (All versions of Python 3.13 have already dropped support for them.) Get it here: > **[Python Release Python 3.12.6](https://www.python.org/downloads/release/python-3126/)** > > The official home of the Python Programming Language 92 commits. ## Python 3.11.10 Python 3.11 joins the elite club of security-only versions with no binary installers. Get it here: > **[Python Release Python 3.11.10](https://www.python.org/downloads/release/python-31110/)** > > The official home of the Python Programming Language 28 commits. ## Python 3.10.15 Get it here: > **[Python Release Python 3.10.15](https://www.python.org/downloads/release/python-31015/)** > > The official home of the Python Programming Language 24 commits. ## Python 3.9.20 Get it here: > **[Python Release Python 3.9.20](https://www.python.org/downloads/release/python-3920/)** > > The official home of the Python Programming Language 22 commits. ## Python 3.8.20 Python 3.8 is very close to End of Life (see [the Release Schedule](https://peps.python.org/pep-0569/)). Will this be the last release of 3.8 ever? We’ll see… but now I think I jinxed it. Get it here: > **[Python Release Python 3.8.20](https://www.python.org/downloads/release/python-3820/)** > > The official home of the Python Programming Language 22 commits. ## Security content in today’s releases - [gh-123678](https://github.com/python/cpython/issues/123678) and [gh-116741](https://github.com/python/cpython/issues/116741): Upgrade bundled libexpat to 2.6.3 to fix [CVE-2024-28757](https://github.com/advisories/GHSA-ch5v-h69f-mxc8), [CVE-2024-45490](https://github.com/advisories/GHSA-4hvh-m426-wv8w), [CVE-2024-45491](https://github.com/advisories/GHSA-784x-7qm2-gp97) and [CVE-2024-45492](https://github.com/advisories/GHSA-5qxm-qvmj-8v79). - [gh-118486](https://github.com/python/cpython/issues/118486): [`os.mkdir()`](https://docs.python.org/3/library/os.html#os.mkdir) on Windows now accepts _mode_ of `0o700` to restrict the new directory to the current user. This fixes CVE-2024-4030 affecting [`tempfile.mkdtemp()`](https://docs.python.org/3/library/tempfile.html#tempfile.mkdtemp) in scenarios where the base temporary directory is more permissive than the default. - [gh-123067](https://github.com/python/cpython/issues/123067): Fix quadratic complexity in parsing `"`-quoted cookie values with backslashes by [`http.cookies`](https://docs.python.org/3/library/http.cookies.html#module-http.cookies). Fixes CVE-2024-7592. - [gh-113171](https://github.com/python/cpython/issues/113171): Fixed various false positives and false negatives in IPv4Address.is\_private, IPv4Address.is\_global, IPv6Address.is\_private, IPv6Address.is\_global. Fixes CVE-2024-4032. - [gh-67693](https://github.com/python/cpython/issues/67693): Fix [`urllib.parse.urlunparse()`](https://docs.python.org/3/library/urllib.parse.html#urllib.parse.urlunparse) and [`urllib.parse.urlunsplit()`](https://docs.python.org/3/library/urllib.parse.html#urllib.parse.urlunsplit) for URIs with path starting with multiple slashes and no authority. Fixes CVE-2015-2104. - [gh-121957](https://github.com/python/cpython/issues/121957): Fixed missing audit events around interactive use of Python, now also properly firing for `python -i`, as well as for `python -m asyncio`. The event in question is `cpython.run_stdin`. - [gh-122133](https://github.com/python/cpython/issues/122133): Authenticate the socket connection for the `socket.socketpair()` fallback on platforms where `AF_UNIX` is not available like Windows. - [gh-121285](https://github.com/python/cpython/issues/121285): Remove backtracking from tarfile header parsing for `hdrcharset`, PAX, and GNU sparse headers. That’s CVE-2024-6232. - [gh-114572](https://github.com/python/cpython/issues/114572): [`ssl.SSLContext.cert_store_stats()`](https://docs.python.org/3/library/ssl.html#ssl.SSLContext.cert_store_stats) and [`ssl.SSLContext.get_ca_certs()`](https://docs.python.org/3/library/ssl.html#ssl.SSLContext.get_ca_certs) now correctly lock access to the certificate store, when the [`ssl.SSLContext`](https://docs.python.org/3/library/ssl.html#ssl.SSLContext) is shared across multiple threads. - [gh-102988](https://github.com/python/cpython/issues/102988): [`email.utils.getaddresses()`](https://docs.python.org/3/library/email.utils.html#email.utils.getaddresses) and [`email.utils.parseaddr()`](https://docs.python.org/3/library/email.utils.html#email.utils.parseaddr) now return `('', '')` 2-tuples in more situations where invalid email addresses are encountered instead of potentially inaccurate values. Add optional _strict_ parameter to these two functions: use `strict=False` to get the old behavior, accept malformed inputs. `getattr(email.utils, 'supports_strict_parsing', False)` can be use to check if the _strict_ paramater is available. This improves the CVE-2023-27043 fix. - [gh-123270](https://github.com/python/cpython/issues/123270): Sanitize names in [`zipfile.Path`](https://docs.python.org/3/library/zipfile.html#zipfile.Path) to avoid infinite loops ([gh-122905](https://github.com/python/cpython/issues/122905)) without breaking contents using legitimate characters. That’s CVE-2024-8088. - [gh-121650](https://github.com/python/cpython/issues/121650): [`email`](https://docs.python.org/3/library/email.html#module-email) headers with embedded newlines are now quoted on output. The [`generator`](https://docs.python.org/3/library/email.generator.html#module-email.generator) will now refuse to serialize (write) headers that are unsafely folded or delimited; see [`verify_generated_headers`](https://docs.python.org/3/library/email.policy.html#email.policy.Policy.verify_generated_headers). That’s CVE-2024-6923. - [gh-119690](https://github.com/python/cpython/issues/119690): Fixes data type confusion in audit events raised by `_winapi.CreateFile` and `_winapi.CreateNamedPipe`. - [gh-116773](https://github.com/python/cpython/issues/116773): Fix instances of `<_overlapped.Overlapped object at 0xXXX> still has pending operation at deallocation, the process may crash`. - [gh-112275](https://github.com/python/cpython/issues/112275): A deadlock involving `pystate.c`’s `HEAD_LOCK` in `posixmodule.c` at fork is now fixed. ## Stay safe and upgrade! Upgrading is highly recommended to all users of affected versions. ## Thank you for your support 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. > **[Welcome to Python.org](https://www.python.org/psf-landing/)** > > The official home of the Python Programming Language – Łukasz Langa @ambv on behalf of your friendly release team, Ned Deily @nad Steve Dower @steve.dower Pablo Galindo Salgado @pablogsal Łukasz Langa @ambv Thomas Wouters @thomas ---
**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:** [September 7, 2024, 10:09am UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/2 "2024-09-07T10:09:53Z")
Is it intentional that 3.9.20 and 3.8.20 don’t include PGP signatures? ---
**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\ **Post date:** [September 7, 2024, 10:28am UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/3 "2024-09-07T10:28:16Z")
Good catch. We are indeed [dropping GPG signatures for Python 3.14](https://github.com/python/release-tools/pull/150), but me not including them for 3.9.20 and 3.8.20 is an omission. Those old versions aren’t using the GitHub Actions automation as the newer releases, and all artifact signing moved there [in March](https://github.com/python/release-tools/pull/71). I uploaded the GPG signatures for both 3.8.20 and 3.9.20 now. The git tags were properly GPG-signed FWIW. ---
**Author:** ![stefanor](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/stefanor/32/9984_2.png) [@stefanor](https://discuss.python.org/u/stefanor)\ **Post date:** [September 7, 2024, 10:39am UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/4 "2024-09-07T10:39:15Z")
Some additional CVEs: > [@ambv](#): > > [gh-123270](https://github.com/python/cpython/issues/123270): Sanitize names in [`zipfile.Path`](https://docs.python.org/3/library/zipfile.html#zipfile.Path) to avoid infinite loops ([gh-122905](https://github.com/python/cpython/issues/122905)) without breaking contents using legitimate characters. That’s CVE-2024-8088 > [@ambv](#): > > [gh-121650](https://github.com/python/cpython/issues/121650): [`email`](https://docs.python.org/3/library/email.html#module-email) headers with embedded newlines are now quoted on output. The [`generator`](https://docs.python.org/3/library/email.generator.html#module-email.generator) will now refuse to serialize (write) headers that are unsafely folded or delimited; see [`verify_generated_headers`](https://docs.python.org/3/library/email.policy.html#email.policy.Policy.verify_generated_headers). That’s CVE-2024-6923 > [@ambv](#): > > [gh-121285](https://github.com/python/cpython/issues/121285): Remove backtracking from tarfile header parsing for `hdrcharset`, PAX, and GNU sparse headers. That’s CVE-2024-6232 ---
**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\ **Post date:** [September 7, 2024, 12:37pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/5 "2024-09-07T12:37:21Z")
Thank you, I updated the list with this information. ---
**Author:** ![stonebig](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/stonebig/32/2796_2.png) [@stonebig](https://discuss.python.org/u/stonebig)\ **Post date:** [September 7, 2024, 2:40pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/6 "2024-09-07T14:40:46Z")
as a cosmetic remark, the release page of Python-3.11.10 embarks the text for a Python-3.10 release [Python Release Python 3.11.10 | Python.org](https://www.python.org/downloads/release/python-31110/) > According to the release calendar specified in [PEP 619](https://www.python.org/dev/peps/pep-0619/), Python 3.10 is now in the “security fixes only” ---
**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\ **Post date:** [September 7, 2024, 2:59pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/7 "2024-09-07T14:59:29Z")
Fixed that, too. Thanks! ---
**Author:** ![mcepl](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/mcepl/32/24095_2.png) [@mcepl](https://discuss.python.org/u/mcepl)\ **Post date:** [September 9, 2024, 1:44pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/8 "2024-09-09T13:44:05Z")
[3.10.13 Documentation](https://docs.python.org/3.10/) is still on 3.10.13. ---
**Author:** ![jamestwebber](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jamestwebber/32/12799_2.png) [@jamestwebber](https://discuss.python.org/u/jamestwebber)\ **Post date:** [September 9, 2024, 2:15pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/9 "2024-09-09T14:15:39Z")
You mean `3.10` documentation? It goes to `3.10.15` for me, maybe just CDN or other caching. ---
**Author:** ![mcepl](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/mcepl/32/24095_2.png) [@mcepl](https://discuss.python.org/u/mcepl)\ **Post date:** [September 9, 2024, 2:19pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/10 "2024-09-09T14:19:06Z")
OK, most likely. ---
**Author:** ![ngoldbaum](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ngoldbaum/32/12276_2.png) [@ngoldbaum](https://discuss.python.org/u/ngoldbaum)\ **Post date:** [September 9, 2024, 4:39pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/11 "2024-09-09T16:39:29Z")
I don’t see this, but [3.13.0rc1 Documentation](https://docs.python.org/3.13/) still points at 3.13.0rc1 for me. Also a stale CDN cache? ---
**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\ **Post date:** [September 9, 2024, 5:51pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/12 "2024-09-09T17:51:09Z")
Docs rebuilds are quite slow due to all languages and formats we build. We’ll get all branches up-to-date this week. ---
**Author:** ![nad](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/nad/32/51_2.png) [@nad](https://discuss.python.org/u/nad)\ **Post date:** [September 9, 2024, 9:07pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/13 "2024-09-09T21:07:41Z")
In the interim while the full doc builds are completing, you can also find archives of the untranslated (English-only) versions of the documentation as they existed at the time of each release [here](https://www.python.org/doc/versions/). Note that these archives do not get updated with post-release changes. ---
**Author:** ![carltongibson](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/carltongibson/32/1648_2.png) [@carltongibson](https://discuss.python.org/u/carltongibson)\ **Post date:** [September 11, 2024, 8:15am UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/14 "2024-09-11T08:15:41Z")
> [@ambv](#): > > Python 3.11 joins the elite club of security-only versions with no binary installers. Could I possibly just ask about this? By [PEP 602](https://peps.python.org/pep-0602/#years-of-full-support-3-more-years-of-security-fixes), for a major Python version… > - During the _first twenty four months_ (2 years) it receives bugfix updates and full releases (sources and installers for Windows and macOS) are made approximately every other month. According to [Status of Python Versions](https://devguide.python.org/versions/#status-of-python-versions) Python 3.11 was released on 2022-10-24 and so I’d expect it to receive a full release and still be in `bugfix` status for another month yet. Is that not correct? Or more, clearly not, so why the early change? Thanks! ---
**Author:** ![carltongibson](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/carltongibson/32/1648_2.png) [@carltongibson](https://discuss.python.org/u/carltongibson)\ **Post date:** [September 11, 2024, 8:18am UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/15 "2024-09-11T08:18:11Z")
Don’t worry, I’ve seen it. Below the _24 months_ quote there’s an extra note: > Note: 2 years of full support start with [Python 3.13](https://peps.python.org/pep-0719/). Python versions 3.9 - 3.12 operate on a calendar with 1½ year of full support, followed by 3½ more years of security fixes. Sorry for the noise. ---
**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:** [September 11, 2024, 12:29pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/16 "2024-09-11T12:29:29Z")
All the 3.8+ docs and translations have now rebuilt (except fr/3.14 and fr/3.13 which is a [known bug](https://github.com/python/docsbuild-scripts/issues/187)). ---
**Author:** ![hroncok](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hroncok/32/18696_2.png) [@hroncok](https://discuss.python.org/u/hroncok)\ **Post date:** [September 11, 2024, 8:23pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/17 "2024-09-11T20:23:32Z")
All 24 (6 Python versions × 4 Fedora Linux versions) Fedora updates are now ready and should be available in the updates-testing (or rawhide) repository within 24 hours. Run `sudo dnf --enablerepo=updates-testing upgrade python3.{8..13}` to get them. ---
**Author:** ![barry](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/barry/32/42_2.png) [@barry](https://discuss.python.org/u/barry)\ **Post date:** [September 11, 2024, 9:23pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/18 "2024-09-11T21:23:15Z")
[CI testing images](https://gitlab.com/python-devs/ci-images/-/tree/main) have been ready for a while\[1\]. * * * 1. technically, they update automatically and within a 4 hour window, but I still have to manually update the `README` ---
**Author:** ![mcepl](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/mcepl/32/24095_2.png) [@mcepl](https://discuss.python.org/u/mcepl)\ **Post date:** [October 2, 2024, 5:20pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/19 "2024-10-02T17:20:45Z")
Was this the last 3.8 release? ---
**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 2, 2024, 5:52pm UTC](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161/20 "2024-10-02T17:52:24Z")
I believe it most likely will be, unless a new security issue comes up before the end of October. [Next page](https://discuss.python.org/t/python-3-13-0rc2-3-12-6-3-11-10-3-10-15-3-9-20-and-3-8-20-are-now-available/63161.md?page=2)