[Python-Dev] GetFinalPathNameByHandleW - what is the minimum windows version python-3.5 will support ?

183 views
Skip to first unread message

Vitaly Murashev

unread,
Jul 19, 2015, 9:40:12 AM7/19/15
to pytho...@python.org
I've just found out that that on Windows internal implementation of python35.dll in posixmodule.c
uses winapi function GetFinalPathNameByHandleW

By the way from MSDN:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364962%28v=vs.85%29.aspx

Minimum supported client
  Windows Vista [desktop apps only]

Minimum supported server
  Windows Server 2008 [desktop apps only]

Does it mean, that Python-3.5 doesn't support any windows versions prior "Windows Vista" and "Windows Server 2008" ?

Best regards,
Vitaly Murashev

Tim Golden

unread,
Jul 19, 2015, 9:52:44 AM7/19/15
to Vitaly Murashev, pytho...@python.org
In essence: yes.

Python's support for Windows is outlined in PEP 11:

https://www.python.org/dev/peps/pep-0011/#microsoft-windows

which establishes that Python drops support for a Windows platform when
Microsoft does. WinXP (somewhat noisily) finished support last year:

http://windows.microsoft.com/en-gb/windows/end-support-help

while Server 2003 -- more quietly; I had to go and look -- came out of
extended support this month:

https://support.microsoft.com/en-us/lifecycle?p1=3198

Since Python 3.5 will come out after both of those platforms have
finished support, there's no guarantee that it will run without error on
those systems.

Obviously, all earlier releases of Python -- including the
long-term-supported 2.7 should continue to work. Any otherwise
undocumented failure to work on older platforms should be raised as a bug.

TJG
_______________________________________________
Python-Dev mailing list
Pytho...@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/dev-python%2Bgarchive-30976%40googlegroups.com

Terry Reedy

unread,
Jul 19, 2015, 2:33:03 PM7/19/15
to pytho...@python.org
On 7/19/2015 9:51 AM, Tim Golden wrote:
>
>
> On 19/07/2015 13:10, Vitaly Murashev wrote:
>> I've just found out that that on Windows internal implementation of
>> python35.dll in posixmodule.c
>> uses winapi function GetFinalPathNameByHandleW
>>
>> By the way from MSDN:
>> https://msdn.microsoft.com/en-us/library/windows/desktop/aa364962%28v=vs.85%29.aspx
>>
>>
>> Minimum supported client
>> Windows Vista [desktop apps only]
>>
>> Minimum supported server
>> Windows Server 2008 [desktop apps only]
>>
>> Does it mean, that Python-3.5 doesn't support any windows versions prior
>> "Windows Vista" and "Windows Server 2008" ?

There was a similar question on python-list about 3.5.0b3 not installing
on XP. This is at least the second of what will be many similar questions.

> In essence: yes.
>
> Python's support for Windows is outlined in PEP 11:
>
> https://www.python.org/dev/peps/pep-0011/#microsoft-windows
>
> which establishes that Python drops support for a Windows platform when
> Microsoft does. WinXP (somewhat noisily) finished support last year:
>
> http://windows.microsoft.com/en-gb/windows/end-support-help

I knew this part.

> while Server 2003 -- more quietly; I had to go and look -- came out of
> extended support this month:
>
> https://support.microsoft.com/en-us/lifecycle?p1=3198

I was not aware of this.

> Since Python 3.5 will come out after both of those platforms have
> finished support, there's no guarantee that it will run without error on
> those systems.

I think this line in the PEP, "Because of this policy, no further
Windows releases need to be listed in this PEP. " is false economy.
Your research on server 2003 should be recorded. (The presence of a 3.5
Server 2003 buildbot, even though not working, might lead one to the
opposite answer.) Even if users ignore the PEP, people answering
questions (like me) try to use it to get definitive answers.

--
Terry Jan Reedy

Chris Angelico

unread,
Jul 19, 2015, 5:33:13 PM7/19/15
to python-dev
On Mon, Jul 20, 2015 at 4:31 AM, Terry Reedy <tjr...@udel.edu> wrote:
> I think this line in the PEP, "Because of this policy, no further Windows
> releases need to be listed in this PEP. " is false economy. Your research on
> server 2003 should be recorded. (The presence of a 3.5 Server 2003 buildbot,
> even though not working, might lead one to the opposite answer.) Even if
> users ignore the PEP, people answering questions (like me) try to use it to
> get definitive answers.

Also, if it comes to that, Server 2003 should probably get mentioned
here, which is where I'd go looking:

https://docs.python.org/dev/whatsnew/3.5.html#unsupported-operating-systems

ChrisA
Reply all
Reply to author
Forward
0 new messages