iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 11: Add note about interpreting current Windows release (#3617) 

PEP 0011: Add note about interpreting current Windows release
This commit is contained in:
Steve Dower 2024-01-10 14:54:09 +00:00 committed by GitHub
parent 6a147eaacb
commit 887cdaa552
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
peps/pep-0011.rst
View File

@ -183,6 +183,13 @@ as the original feature release, even if no longer supported by Microsoft.
New versions of Windows released while CPython is in maintenance mode New versions of Windows released while CPython is in maintenance mode
may be supported at the discretion of the core team and release manager. may be supported at the discretion of the core team and release manager.
As of 2024, our current interpretation of Microsoft's lifecycles is that
Windows for IoT and embedded systems is out of scope for new CPython releases,
as the intent of those is to avoid feature updates. Windows Server will usually
be the oldest version still receiving free security fixes, and that will
determine the earliest supported client release with equivalent API version
(which will usually be past its end-of-life).
Each feature release is built by a specific version of Microsoft Each feature release is built by a specific version of Microsoft
Visual Studio. That version should have mainstream support when the Visual Studio. That version should have mainstream support when the
release is made. Developers of extension modules will generally need release is made. Developers of extension modules will generally need