launcher hides output and ignores command line arguments

[anatoly techtonik]

I am trying to figure out why program installed with pip doesn't start. But launcher hides all the output.

https://github.com/spyder-ide/spyder/issues/3242

If I remove pythonw.exe, the launcher shows this:

For me the behavior of launcher should be configurable. Ideally, it should not use pythonw.exe if run from console. Or if command line is supplied or a stacktrace is written to stdout some popup window should show the output. And of course, if application needs to pass errors silently it should have an option (with an ability to access stdout buffer anyway).

So is anything of this possible?

[Vinay Sajip]

The launcher just uses what is in the shebang line - it doesn't try to be too clever. It's up to whatever creates the script to use the appropriate shebang line.

It's perfectly reasonable to start a windowed application from a console, in which case pythonw.exe should be used.

The correct answer is for windowed applications (where console output isn't available) to use mechanisms such as logging to allow diagnosis of startup (and later) problems.