This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients gvanrossum, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-12-15.19:07:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639595221.47.0.522675592351.issue46088@roundup.psfhosted.org>
In-reply-to
Content
I am trying to build under Visual Studio (the 2019 release) and I'm encountering the following weird issue. In the project file PCbuild\_freeze_module.vcxproj there's a command that runs the Tools\scripts\deepfreeze.py script to generate some code.

The invocation is as follows:

    <Exec Command='$(PythonForBuild) "$(PySourcePath)Tools\scripts\deepfreeze.py" "%(None.OutFile)" "-m" "%(None.ModName)" -o "%(None.IntFile)"' />

Apparently the PythonForBuild variable is unset, because this steps is trying to *open* the deepfreeze.py script using the default app for opening .py files, which in my case is VS Code.

It seems that when using PCbuild\build.bat, PythonForBuild is set (on line 121) to %PYTHON%, which presumably points to some Python interpreter. But apparently when the build is driven by VS, this is not executed and now we're stuck.

Is there someone with enough MSBUILD skills to help me fix this?
History
Date User Action Args
2021-12-15 19:07:01gvanrossumsetrecipients: + gvanrossum, paul.moore, tim.golden, zach.ware, steve.dower
2021-12-15 19:07:01gvanrossumsetmessageid: <1639595221.47.0.522675592351.issue46088@roundup.psfhosted.org>
2021-12-15 19:07:01gvanrossumlinkissue46088 messages
2021-12-15 19:07:01gvanrossumcreate