[issue45978] deepfreeze opaquely fails on Windows when building from Visual Studio

[Dennis Sweeney]

Dennis Sweeney  added the comment:

This was fixed by https://github.com/python/cpython/pull/30143

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45978] deepfreeze opaquely fails on Windows when building from Visual Studio

[Christian Heimes]

Christian Heimes  added the comment:

Main requires a recent version of Python in order to bootstrap the build 
process. I just re-introduced _bootstrap_python for configure & make builds in 
bpo-45950. Could somebody with a Windows system re-add _bootstrap_python to 
Windows build process? bpo-45850 and bpo-45873 have more context.

--
nosy: +christian.heimes

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45978] deepfreeze opaquely fails on Windows when building from Visual Studio

[Dennis Sweeney]

Dennis Sweeney  added the comment:

Actually, it seems $(PythonForBuild) is already used everywhere, it's just that 
$(PythonForBuild) is giving the empty string when VS uses it.

On the other hand, PCBuild/build.bat sets $(PythonForBuild) by calling out to 
find_python.bat, and that works great.

So perhaps the VS build should just be made to invoke find_python.bat.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45978] deepfreeze opaquely fails on Windows when building from Visual Studio

[Dennis Sweeney]

Dennis Sweeney  added the comment:

Sure enough, if I go to "Choose Default Apps by File Type" in Windows settings 
and associate ".py" --> "Notepad", then Visual studio keeps opening Notepad 
windows during build.

Can the Visual Studio build configurations be made to run python scripts as 
"SOME_SPECIFIC_PYTHON_EXECUTABLE ./script.py" or perhaps "py ./script.py" 
instead of just "./script.py"?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45978] deepfreeze opaquely fails on Windows when building from Visual Studio

[Dennis Sweeney]

Dennis Sweeney  added the comment:

I think I've been getting similar issues for a little while that I've been able 
to work around until now. If I git checkout 3.10 and then hit the "Local 
Windows Debugger" button, I get this:

Build started...
1>-- Build started: Project: pythoncore, Configuration: Debug x64 --
1>Killing any running python_d.exe instances...
1>Regenerate opcode.h opcode_targets.h
1>C:\Users\sween\Source\Repos\temp\cpython\PCbuild\regen.targets(62,5): error 
MSB3073: The command " Tools\scripts\generate_opcode_h.py Lib\opcode.py 
Include\opcode.h" exited with code 103.
1>Done building project "pythoncore.vcxproj" -- FAILED.
2>-- Build started: Project: _ctypes, Configuration: Debug x64 --
3>-- Build started: Project: python, Configuration: Debug x64 --
== Build: 0 succeeded, 3 failed, 0 up-to-date, 0 skipped ==

However, if I then run .\PCbuild\build.bat, and then hit the "Local Windows 
Debugger" button, the build succeeds.

Is there some difference in which python executable is chosen to run .py files 
between build.bat versus what Visual Studio does?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45978] deepfreeze opaquely fails on Windows when building from Visual Studio

[Dennis Sweeney]

New submission from Dennis Sweeney :

I'd love to know if there is something I'm doing wrong, but with recent 
deepfreeze changes, my Visual Studio 2019 setup has been having trouble build 
things. It seems PCBuild/build.bat works perfectly and all tests pass and 
everything, but using the GUI in Visual Studio 2019 to build with the "Local 
Windows Debugger" green play button leads to a build failure. It gives the 
following output:

Build started...
1>-- Build started: Project: _freeze_module, Configuration: Debug x64 --
1>_freeze_module.vcxproj -> 
C:\Users\sween\Source\Repos\temp\cpython\PCbuild\amd64\_freeze_module_d.exe
1>C:\Users\sween\Source\Repos\temp\cpython\PCbuild\_freeze_module.vcxproj(413,5):
 error MSB3073: The command " 
"C:\Users\sween\Source\Repos\temp\cpython\Tools\scripts\deepfreeze.py" 
"C:\Users\sween\Source\Repos\temp\cpython\Python\frozen_modules\importlib._bootstrap.h"
 "-m" "importlib._bootstrap" -o 
"C:\Users\sween\Source\Repos\temp\cpython\PCbuild\obj\311amd64_Debug\_freeze_module\importlib._bootstrap.g.h""
 exited with code 103.
1>Done building project "_freeze_module.vcxproj" -- FAILED.
== Build: 0 succeeded, 1 failed, 3 up-to-date, 0 skipped ==

I wonder if it has something to do with how .py files are set to open? 
(shouldn't that be made not to matter?)

Attached are my more detailed steps to reproduce the failure.

--
components: Build, Windows
files: reproducer.txt
messages: 407648
nosy: Dennis Sweeney, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: deepfreeze opaquely fails on Windows when building from Visual Studio
type: compile error
versions: Python 3.11
Added file: https://bugs.python.org/file50474/reproducer.txt

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com