[PyInstaller] Tkinter opening a second window after made into an executable.

I am creating an app that can compile python projects into an exe, I am using Tkinter as for the GUI. I'm using PyInstaller within the python code to do this but when tested using the exe version of this project, it creates another window when I press 'Submit'. I cannot figure out why. The proj

[PyInstaller] Re: pyinstaller: error: unrecognized arguments: B:/coding/py2exe/test.py

Perfect thank you. On Sunday, 24 September 2023 at 09:59:39 UTC+1 bwoodsend wrote: > It’s your dist/work/spec path parameters causing the problem. They need to > be written as either '--distpath=B:\\coding\\py2exe' or two separate > strings '--distpath', 'B:\\coding\\py2exe'. The command line e

Re: [PyInstaller] Re: Application creating second instance of self

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

[PyInstaller] Re: PyiFrozenImporter cannot handle module

I can’t get the issue to occur using the latest PyInstaller and compound_split. Line 10 of compound_split\char_split.py is import compound_split.char_split so running pyinstaller on a script containing just that line should be enough to trigger the error. Can you confirm if that is the case f

Re: [PyInstaller] Re: Application creating second instance of self

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

Re: [PyInstaller] Re: Application creating second instance of self

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 avai

[PyInstaller] Re: _internal

If 6.0.0 breaks your data file locating then your code is broken and PyInstaller’s change is merely shedding light on it. If you anchor resource paths using __file__ like the docs tell you to then it shouldn’t matter whic

[PyInstaller] _internal

hello, can you help me? how to configure pyinstaller so that it does not create and move exe files to _internal, because of this my program does not see the Data folder where important files for my program are located, I'm currently using version 6.0.0. This was not the case in older versions. -

Re: [PyInstaller] Trojan detected in 5.13?

Guys, good news, it had taken a little time, as I had to contact the virus scanner company twice, but today I got the message, that the issue has been handled and indeed I did not get any false positive with Virustotal for said 5.13.0 anymore! Cheers, Dominik Dominik Niedenzu schrieb am Mittwoc

Re: [PyInstaller] Re: Application creating second instance of self

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 thi