-
Relevant doc page: Spec file in question:
The application is supposed to log to STDOUT and STDERR, but it never does, powershell just instantly returns when launching the app. The internal logging(which logs both to stderr and the app itself) seems to keep working even when pyinstalled. What am I doing wrong here? I would like the app to display stderr when specifically launched from a terminal, but not launch an extra terminal window when EXE is double clicked - is there no way to have my cake and eat it too? Is there no way to build the application in both modes, and perhaps at least only execute the logging one with some additional |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Executables built with
Short of building two executables - one with Back before Windows Terminal was the default, you could sort of emulate what you want by building a console-enabled application ( |
Beta Was this translation helpful? Give feedback.
Executables built with
/SUBSYSTEM:WINDOWED
do not have console attached, even if you launch them from console. Similarly, they launch in the background w.r.t. to the console that you launched them from, hence the "instant return".Short of building two executables - one with
console=True
and one withconsole=False
(s…