Sadly, there are about 250 matches to that call within all the libraries
packaged in my application! I did some more logging. The last time
subprocess.run() gets called before a second instance of my application is
initialized is in the following custom logging I did...
*** check_output command
On Tue, Sep 26, 2023 at 12:52 AM bwoodsend wrote:
> That sounds like a red herring. It’s specifically
> subprocess.run([sys.executable,
> ...]) that we’re interested in — any other command should run fine under
> PyInstaller.
>
indeed -- a search for "sys.executable" may find the culprit.
-CHB
Ok, looks like I'll have to do some more digging.
The other issue I'm running into has to do with TensorFlow. My goal is to
create a single windowed executable with no console. Unfortunately, when I
package my application without a console, I run into this error:
WARNING - AutoGraph is not
That sounds like a red herring. It’s specifically
subprocess.run([sys.executable,
...]) that we’re interested in — any other command should run fine under
PyInstaller.
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To unsubscribe from
I have found at least one of the issues. I dumped the stack trace in
subprocess.run() to find out who was calling it. During my code, at some
point, a numpy function called check_support_sve() gets called. It resides
in numpy/testing/_private/utils.py. Here's the code
def check_support_sve():
Thanks so much for the response! I have narrowed it down to the ultralytics
library but I haven't been able to identify where in that code it's calling
a subprocess. I'll try to investigate some more.
On Sun, Sep 24, 2023, 1:59 AM bwoodsend wrote:
> I’ve read some about how sys.executable() is
I’ve read some about how sys.executable() is different when you run a
packaged application, so I’m sure that could be playing a role, but I have
no idea how to fix that.
A library that tries to run Python subprocesses will cause a PyInstaller
application to keep spawning itself because
