[issue39952] Using VS2019 to automatically build Python3 and it failed to build

Steve Dower added the comment: I think we can close it. -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___

[issue39952] Using VS2019 to automatically build Python3 and it failed to build

Irit Katriel added the comment: 3.6 is no longer maintained. Can we close this now, or is this a problem on newer versions as well? -- nosy: +iritkatriel resolution: -> out of date status: open -> pending ___ Python tracker

[issue39952] Using VS2019 to automatically build Python3 and it failed to build

Lin Gao added the comment: Hi Steve, Sorry for the delay. Thanks for your information and help. We mainly use open source projects to test the vs compiler backend. Now is the migration for testing and need to replace vs2017 with vs2019. Currently we used the second work around you provide

[issue39952] Using VS2019 to automatically build Python3 and it failed to build

Steve Dower added the comment: Hi Lin, please look me up on Teams and we can chat about this. I haven't heard about this effort and I'd love to know what you're working on. --- The last error is because the VS Setup team has never updated their package to include v142 libs (https://www.nug

[issue39952] Using VS2019 to automatically build Python3 and it failed to build

Lin Gao added the comment: Hi, Thanks for your reply and info! I've tried to use you provided --no-tkinter to re-build python3.6. And now There is only one error left. Have you encountered this problem? build -e -r --no-tkinter -v "/p:PlatformToolset=v142" "/p:WindowsTargetPlatformVersion

[issue39952] Using VS2019 to automatically build Python3 and it failed to build

Zachary Ware added the comment: (FTR, removing yourself from the "nosy list" means you won't get any responses to your issue, so I've added you back :)) This appears to be a problem with building Tcl/Tk. If you don't need the tkinter module, you can try adding the `--no-tkinter` flag to you

[issue39952] Using VS2019 to automatically build Python3 and it failed to build

Change by Lin Gao : -- nosy: -Lin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/ma

[issue39952] Using VS2019 to automatically build Python3 and it failed to build

New submission from Lin Gao : We (the MSVC ++ team) is trying to use VS2019 to replace VS2017 to automatically build Python3(branch 3.6)on Windows. First build failed with error MSB8036: The Windows SDK version 10.0.10586.0 was not found. So we modified the build command line to 'build -e -r