[Python-Dev] Windows XP, Python 3.5 and PEP 11

[Mark Lawrence]

On 17/06/2014 08:03, Victor Stinner wrote:
> 2014-06-17 7:01 GMT+02:00 Tim Golden <mail at timgolden.me.uk>:
>> On 17/06/2014 04:08, Zachary Ware wrote:
>>> This was recently discussed in the "Moving Python 3.5 on Windows to a
>>> new compiler" thread, where Martin declared XP support to be ended
>>> [1].  I believe Tim Golden is the only resident Windows dev from whom
>>> I haven't seen at least implicit agreement that XP doesn't need
>>> further support, so I'd say our support for XP is well and truly dead
>>> :)
>>>
>>> In any case, surely anyone stuck with XP can be happy with Python 3.4.
>>> I'm perfectly fine with 3.2 on Win2k!
>>>
>>
>> I think we're justified in dropping XP support, for all the reasons others
>> have given.
>
> Would you be ok to make this official by adding Windows XP explicitly
> to the PEP 11? (I can do the change, I'm just asking for a
> confirmation.)
>

 From PEP 11 the entire "Microsoft Windows" section.  Please see the 
third paragraph.

"Microsoft has established a policy called product support lifecycle 
[1]. Each product's lifecycle has a mainstream support phase, where the 
product is generally commercially available, and an extended support 
phase, where paid support is still available, and certain bug fixes are 
released (in particular security fixes).

Python's Windows support now follows this lifecycle. A new feature 
release X.Y.0 will support all Windows releases whose extended support 
phase is not yet expired. Subsequent bug fix releases will support the 
same Windows releases as the original feature release (even if the 
extended support phase has ended).

Because of this policy, no further Windows releases need to be listed in 
this PEP.

Each feature release is built by a specific version of Microsoft Visual 
Studio. That version should have mainstream support when the release is 
made. Developers of extension modules will generally need to use the 
same Visual Studio release; they are concerned both with the 
availability of the versions they need to use, and with keeping the zoo 
of versions small. The Python source tree will keep unmaintained build 
files for older Visual Studio releases, for which patches will be 
accepted. Such build files will be removed from the source tree 3 years 
after the extended support for the compiler has ended (but continue to 
remain available in revision control)."

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com