PYQT5 QThread: Destroyed while thread is still running

Yok0 · S SGaist 25 Jul 2020, 13:26

@SGaist sure QProcessEnvironment is a better way.
Also, I thought I could find the path programmatically like using shutil.which("app") but when the program is bundled and launched from the myApp.app. shutil.which() can't find program in /usr/local... it only find os based executable like ls.

SGaist · wrote on 25 Jul 2020, 18:46

How are you bundling it ?
Is it a compiled executable ?

Yok0 · wrote on 25 Jul 2020, 18:59

I use fbs to package it for macos, it gives me an executable myApp.app

SGaist · wrote on 25 Jul 2020, 20:21

I meant the application you execute with QProcess.

Yok0 · 26 Jul 2020, 12:23

Oh it's youtube-dl and it's work fine like I said if I specify the absolute path of the executable in this case it's /usr/local/bin/...
Sorry it's not related to QProcess but in some situations youtube-dl needs ffmpeg so I would check if it's installed on the system. That's why I use shutil.which('ffmpeg').
It works great in my virtualenv but after compiled the program, shutil can't find the path of ffmpeg. Somehow it can't find apps in /usr/local/bin even if it is in $PATH. However it will find os based app like "ls", "mkdir"...

JonB · 26 Jul 2020, 13:27

@Yok0
Are you certain /usr/local/bin is on your PATH, really? Things like ls/mkdir are in /bin and/or /usr/bin, which will be on $PATH, maybe /usr/local/bin is not.

Yok0 · 26 Jul 2020, 14:16

@JonB Yep! I did checked it.
In my app I tried to displayed my $PATH with os.environ.get('PATH'). When I run it in my virtualenv, it shows me to correct $PATH with /usr/bin, /usr/bin/local/, .cargo/bin so on and so forth BUT after bundling the project in an executable, that same command only returns /usr/bin:/bin:/usr/sbin:/sbin
The weird thing is that the app is run by the same user in venv and as a executable. The $PATH is somehow overridden.

JonB · 26 Jul 2020, 16:20

@Yok0
Yes, virtualenv's job is to set your path. It is not surprising it is different from path outside venv.

So your problem is that the executable you wish to run lives in a directory which is not on your usual path.

Yok0 · 26 Jul 2020, 17:41

@JonB mhm indeed the working direcory of the executable become /
instead of /Users/foo .. obvious, thanks.

JonB · 26 Jul 2020, 19:56

@Yok0
You're not executing this as root/su on the installed system, are you?

Yok0 · 27 Jul 2020, 08:17

@JonB nop regular user

JonB · Y Yok0 26 Jul 2020, 19:56

@Yok0
Then there's something "odd" about / being the working directory! The whole thing might make sense as root, as he may not have /usr/local/bin on his PATH.