Question for potential python development contributions on Windows

The Python Developers Guide specifically states to get VS2017 for developing or enhancing python on a Windows system. Is it still correct to specifically use VS2017 , or is VS2019 also acceptable? I ask this because I know that the *.vcproj files and other build-environment files have changed format pretty dramatically over the many releases of VS. If a potential new contribution targeted for current and future python will require new build environment files, I wouldn't want to have to "down release" those files (or expect core dev's to do it) at or after submission to the community for approval. Much better to use the same setup as core dev's use than to introduce up-level differences in the build environment. IOW, for new releases on Windows are core dev's still using VS2017 and so potential contributors should also use that version, or has the core dev's process for Windows releases been updated to use VS2019? Peter --

On 20 May 2021, at 07:03, pjfarley3@earthlink.net wrote:
The Python Developers Guide specifically states to get VS2017 for developing or enhancing python on a Windows system.
Is it still correct to specifically use VS2017 , or is VS2019 also acceptable?
We have to update the devguide. VS 2019 is supported, probably even recommended, as long as the C++ tools are v14.x. Cheers, Łukasz

On Mon, May 24, 2021 at 6:40 PM Łukasz Langa <lukasz@langa.pl> wrote:
On 20 May 2021, at 07:03, pjfarley3@earthlink.net wrote:
The Python Developers Guide specifically states to get VS2017 for developing or enhancing python on a Windows system.
Is it still correct to specifically use VS2017 , or is VS2019 also acceptable?
We have to update the devguide. VS 2019 is supported, probably even recommended, as long as the C++ tools are v14.x.
Also of note is this page: https://wiki.python.org/moin/WindowsCompilers It lists Visual Studio versions for different Python versions (for compiling extensions), but it stops at 3.8. ChrisA

From: Łukasz Langa <lukasz@langa.pl> Sent: Monday, May 24, 2021 4:37 AM To: pjfarley3@earthlink.net Cc: python-dev@python.org Subject: Re: [Python-Dev] Question for potential python development contributions on Windows
On 20 May 2021, at 07:03, mailto:pjfarley3@earthlink.net wrote:
The Python Developers Guide specifically states to get VS2017 for developing or enhancing python on a Windows system.
Is it still correct to specifically use VS2017 , or is VS2019 also acceptable?
We have to update the devguide. VS 2019 is supported, probably even recommended, as long as the C++ tools are v14.x.
Thank you Łukasz, I was hoping that would be the answer. How does one verify whether the C++ tools are 14.x, or is that just the usual for recent versions of VS2019? Peter

How do you check that the C++ tools are v14.x? On Mon, May 24, 2021 at 1:43 AM Łukasz Langa <lukasz@langa.pl> wrote:
On 20 May 2021, at 07:03, pjfarley3@earthlink.net wrote:
The Python Developers Guide specifically states to get VS2017 for developing or enhancing python on a Windows system.
Is it still correct to specifically use VS2017 , or is VS2019 also acceptable?
We have to update the devguide. VS 2019 is supported, probably even recommended, as long as the C++ tools are v14.x.
Cheers, Łukasz _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/UCSCYMMJ... Code of Conduct: http://python.org/psf/codeofconduct/
-- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-c...>

When you're installing Visual Studio the C++ tools version is listed under the selected components as "v14x". However, at this stage, the *only* version in circulation is 14.x - mine shows v142. Until the 14 changes to a "15", it will be binary compatible and so you can use any version at all to build CPython and/or extension modules. Our official releases are always using relatively up-to-date compilers, but provided the compatibility is maintained on Microsoft's side, there's no need to worry about the specific versions. Cheers, Steve On 5/24/2021 4:49 PM, Guido van Rossum wrote:
How do you check that the C++ tools are v14.x?
On Mon, May 24, 2021 at 1:43 AM Łukasz Langa <lukasz@langa.pl <mailto:lukasz@langa.pl>> wrote:
On 20 May 2021, at 07:03, pjfarley3@earthlink.net <mailto:pjfarley3@earthlink.net> wrote:
The Python Developers Guide specifically states to get VS2017 for developing or enhancing python on a Windows system.____ __ __ Is it still correct to specifically use VS2017 , or is VS2019 also acceptable?
We have to update the devguide. VS 2019 is supported, probably even recommended, as long as the C++ tools are v14.x.
Cheers, Łukasz
participants (5)
-
Chris Angelico
-
Guido van Rossum
-
pjfarley3@earthlink.net
-
Steve Dower
-
Łukasz Langa