[WIP] bpo-32592: Drop support for Windows Vista#5231
Conversation
Windows Vista extended support ended in April 2017. As stated in PEP 11, Python 3.7 drops support for Windows Vista and now requires Windows 7 or newer.
|
Hum, the change should be mentionned in Doc/whatsnew/3.7.rst. |
Sorry, something went wrong.
|
AppVeyor compilation failed with: "C:\Program Files (x86)\Windows Kits\10\Include\10.0.16299.0\shared\sdkddkver.h(289): fatal error C1189: #error: NTDDI_VERSION setting conflicts with _WIN32_WINNT setting [C:\projects\cpython\PCbuild\pythoncore.vcxproj]" |
Sorry, something went wrong.
|
@vstinner There is some references to Vista in the |
Sorry, something went wrong.
Rephrase also a comment in condvar.h.
I don't know this directory, so I prefer to leave it unchanged. |
Sorry, something went wrong.
@zooba: Do you understand why my change breaks the compilation? |
Sorry, something went wrong.
|
"posixmodule.obj : error LNK2001: unresolved external symbol _GetMaximumProcessorCount [C:\projects\cpython\PCbuild\pythoncore.vcxproj]" Oh, my posixmodule.c change doesn't work :-( Extract of pythoninfo: I understand that AppVeyor runs Windows 10 and Python was built by Visual Studio 2017 https://msdn.microsoft.com/fr-fr/library/windows/desktop/dd405489(v=vs.85).aspx "Remarks: To compile an application that uses this function, set _WIN32_WINNT >= 0x0601. For more information, see Using the Windows Headers." Aha. I need to try to understand why changing _WIN32_WINNT failed. But my Windows VM is down :-) |
Sorry, something went wrong.
|
Hum, I'm not sure that my PR is correct anymore. I change its status to WIP, I will rework on it, once I get again access to a Windows VM to fix my PR. |
Sorry, something went wrong.
|
Some news about this PR ?
…--
Stéphane Wirtel - http://wirtel.be - @matrixise
|
Sorry, something went wrong.
Windows Vista extended support ended in April 2017. As stated in PEP
11, Python 3.7 drops support for Windows Vista and now requires
Windows 7 or newer.
https://bugs.python.org/issue32592