Text of peps.python.org › pep-0011 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PEP 11 – CPython platform support | peps.python.org

PEP 11 – CPython platform support PEP 11 – CPython platform support Author : Martin von Löwis <martin at v.loewis.de>, Brett Cannon <brett at python.org> Status : Active Type : Process Created : 07-Jul-2002 Post-History : 18-Aug-2007 , 14-May-2014 , 20-Feb-2015 , 10-Mar-2022 , 21-Nov-2025 Table of Contents Abstract Rationale Support tiers Tier 1 Tier 2 Tier 3 Unsupported platforms Notes Microsoft Windows POSIX Legacy C Locale WASI Unsupporting platforms No-longer-supported platforms Discussions Copyright Abstract This PEP documents how an operating system (platform) becomes supported in CPython, what platforms are currently supported, and documents past support.

Rationale Over time, the CPython source code has collected various pieces of platform-specific code, which, at some point in time, was considered necessary to use CPython on a specific platform. Without access to this platform, it is not possible to determine whether this code is still needed. As a result, this code may either break during CPython’s evolution, or it may become unnecessary as the platforms evolve as well.

Allowing these fragments to grow poses the risk of unmaintainability: without having experts for a large number of platforms, it is not possible to determine whether a certain change to the CPython source code will work on all supported platforms. To reduce this risk, this PEP specifies what is required for a platform to be considered supported by the CPython core team, as well as providing a procedure to remove code for platforms with few or no CPython users.

On the other hand, allowing these fragments in the main repository can promote collaboration, can help identify non-portable parts of the code base, and is necessary for bootstrapping support for a “new” platform. This PEP specifies what it means for a platform to be “unsupported”, and how the core team handles code for such platforms. This PEP also explicitly lists what platforms are directly supported by the CPython development team.

Support tiers Platform support is broken down into tiers . Each tier comes with different requirements which lead to different promises being made about support. To be promoted to a tier, steering council support is required and is expected to be driven by team consensus. Demotion to a lower tier occurs when the requirements of the current tier are no longer met for a platform for an extended period of time based on the judgment of the release manager or steering council.

For platforms which no longer meet the requirements of any tier by b1 of a new feature release, an announcement will be made to warn the community of the pending removal of support for the platform (e.g. in the b1 announcement). If the platform is not brought into line for at least one of the tiers by the first release candidate, it will be listed as unsupported in this PEP. Tier 1 STATUS CI failures block releases. Changes which would break the main branch are not allowed to be merged; any breakage should be fixed or reverted immediately.

All core developers are responsible to keep main , and thus these platforms, working. Failures on these platforms block a release . Target Triple Notes aarch64-apple-darwin clang aarch64-unknown-linux-gnu glibc, gcc i686-pc-windows-msvc x86_64-pc-windows-msvc x86_64-unknown-linux-gnu glibc, gcc Tier 2 STATUS Must have a reliable buildbot. At least two core developers are signed up to support the platform. Changes which break any of these platforms are to be fixed or reverted within 24 hours .

Failures on these platforms block a release . Target Triple Notes Contacts aarch64-unknown-linux-gnu glibc, clang Victor Stinner, Gregory P. Smith aarch64-pc-windows-msvc Steve Dower, Diego Russo, Chris Eibl wasm32-unknown-wasip3 WASI SDK, Wasmtime Brett Cannon, Michael Droettboom, Savannah Ostrowski x86_64-apple-darwin macOS, clang Sam Gross, Barry Warsaw, Ronald Oussoren x86_64-unknown-linux-gnu glibc, clang Victor Stinner, Gregory P.

Smith Tier 3 STATUS Must have a reliable buildbot. At least one core developer is signed up to support the platform. No response SLA to failures. Failures on these platforms do not block a release. Target Triple Notes Contacts aarch64-linux-android Malcolm Smith, Russell Keith-Magee arm64-apple-ios iOS on device Russell Keith-Magee, Ned Deily arm64-apple-ios-simulator iOS on M1 macOS simulator Russell Keith-Magee, Ned Deily armv7l-unknown-linux-gnueabihf 32-bit Raspberry Pi OS, gcc Gregory P.

Smith aarch64-unknown-linux-gnu 64-bit Raspberry Pi OS, gcc Savannah Ostrowski, Stan Ulbrych powerpc64le-unknown-linux-gnu glibc, clang glibc, gcc Victor Stinner Victor Stinner riscv64-unknown-linux-gnu glibc, clang glibc, gcc Stan Ulbrych, Emma Smith Stan Ulbrych, Emma Smith s390x-unknown-linux-gnu glibc, gcc Victor Stinner wasm32-unknown-emscripten emcc Russell Keith-Magee x86_64-linux-android Malcolm Smith, Russell Keith-Magee x86_64-unknown-freebsd BSD libc, clang Victor Stinner Unsupported platforms All platforms not listed in the above tiers are unsupported by the core team.

The core team does not develop and test on such platforms, and so they cannot provide any promises that Python will work on them. However, the code base does include unsupported code – that is, code specific to unsupported platforms. Contributions in this area are welcome as long as they: pose a minimal maintenance burden to the core team, and benefit substantially more people than the contributor. We assume contributors are able to maintain modifications/patches, test patched builds, redistribute modified code, make promises to their users, and otherwise support “their” platform.

With that in mind, it is generally unnecessary to backport unsupported fixes to CPython’s maintenance branches. Unsupported code that does cause a maintenance burden, or obstructs general improvements, may be rejected or removed from the code base without a deprecation process. Core team members that do this intentionally are encouraged to notify people listed in the Ports and contacts list in the Python developer’s guide, to review any submitted fixes (if unobtrusive), and to consider adding configuration or extension capabilities necessary for workarounds.

People interested in unsupported platforms may add themselves to the Ports and contacts list to request that they be notified on issues related to “their” platform. There is, however, no formal guarantee that they will be notified. Platforms not listed in this PEP may also be supported by the wider Python community in other ways. If your desired platform is not listed above, please perform a search online to see if someone is already providing support in some form.

Notes Microsoft Windows Windows versions prior to Windows 10 follow Microsoft’s Fixed Lifecycle Policy , with a mainstream support phase for 5 years after release, where the product is generally commercially available, and an additional 5 year extended support phase, where paid support is still available and certain bug fixes are released. Extended Security Updates (ESU) is a paid program available to high-volume enterprise customers as a “last resort” option to receive certain security updates after extended support ends.

ESU is considered a distinct phase that follows the expiration of extended support. Windows 10 and later follow Microsoft’s Modern Lifecycle Policy , which varies per-product, per-version, per-edition and per-channel. Generally, feature updates (1709, 22H2) occur every 6-12 months and are supported for 18-36 months; Server and IoT editions, and LTSC channel releases are supported for 5-10 years, and the latest feature release of a major version (Windows 10, Windows 11) generally receives new updates for at least 10 years following release.

Microsoft’s Windows Lifecycle FAQ has more specific and up-to-date guidance. CPython’s Windows support currently follows Microsoft’s lifecycles. A new feature release X.Y.0 will support all Windows versions who

The rest of this page is on the live site.