PyApp with GUI program - disable console on Windows about pyapp HOT 4 CLOSED

I agree with your worries. These started to come up when I was testing the implementation as well. There's a longer explanation / write up in the PR, see #97. The short is:

• targeting windows_subsystem = "windows" for PyApp is not a good idea, since setup, management, etc. require the console.
• GUIs can be run in the run_project with pythonw.exe. A console appears now briefly when starting the app but then disappears. I think that's a fair trade of. This also means that all the great things with PyApp stay, like installation splash screen, self management from the console, etc.

from pyapp.

It's been a while since I used pyapp and I might be wrong on a few comments, but I have some questions/worries:

IIRC if we open two processed of pyapp and the venv installation wasn't finished, one or both will fail. I had to run app.exe self restore command on a terminal to start fresh (or even manually delete the virtualenv folder)

Is there a mechanism to automatically run the self restore command on installation or imports failure, and could this be an issue when a user clicks the app, it takes a while to load/install and they spawn many processes of it?

~

For that, it's probably feature creep, but a quick pyinstaller-like splash screen would be nice to have-

-or even detecting same-name processes of the pyapp binary already running and giving preference to the older one*

^{*This might NOOP and require task managers strategy of sending a challenge signal to the process we might replace to detect if softlocked or healthy}

from pyapp.

about subsystem = "windows"
I have a rust project about a caller wrapper in rust
it may can help you doing it

https://github.com/shenjackyuanjie/wrapper-rs

from pyapp.

Resolved by #97

from pyapp.