- Eon timer 2.0 i open it but it just closes right away .exe#
- Eon timer 2.0 i open it but it just closes right away install#
- Eon timer 2.0 i open it but it just closes right away code#
Hopefully someone else finds this useful.Assuming that takes, Ubuntu will be your default.
I've been coming back and trying to solve this problem for MONTHS. My program also now opens from double clicking the app as intended.
Macs will find the location properly, and you will be able to reference the same file every time you open the program. This solution will make any created file drop right next to your Unix Executable in the Mac app bundle, and NOT in the random temp file. To resolve this issue use the following snippet: import sysĬurrent_Path = os.path.dirname(sys.executable)Ĭurrent_Path = str(os.path.dirname(_file_))Īnd then connect it to your log/shelf/save file names accordingly: shelfFile = shelve.open(os.path.join(Current_Path, 'example_data')) Some newer macs don't have permission to write there, and additionally you get a new temp folder every time you open the program, making it useless for logs or saves. You COULD use _meipass to guide your log/shelf file (or whatever) to the correct temp folder, but this causes other problems.
For some reason Macs can find their way to the correct run-time temp folder when run from the unix executable, but get lost when run from the app. When you run a pyinstaller build Macs will do all their run-time things in a random temp folder. Your spec file looks perfect to me.įor me I traced the issue down to my program having to write files to the disk, whether it be creating a log file, or creating a shelf file (which I use for save date). Like you, the Mac build app closes after opening, but if you navigate through the app folder and open the Unix Executable directly it runs flawlessly. This is defined by a Pyinstaller build that works fine on Windows and Linux, but closes immediately after building on Mac. The -i flag is for adding an icon to my program.Īfter many hours scouring/tinkering, I think I have found a solution!!
Eon timer 2.0 i open it but it just closes right away .exe#
exe instead of having a lot of files surrounding my. The -F flag was to bundle everything into one. It looked like this: pyinstaller -c -F -i cm_icon.ico console_monopoly.py Note: On Windows, this option will have no effect if the first script is a ‘.pyw’ file. exe to open a console and keep it open using the -c flag. I also tried a different command-line command. I think that this was my main thing because the first time I installed it, I believe my antivirus prevented some of the components from installing correctly and when I reinstalled it, it probably patched in the holes.
Eon timer 2.0 i open it but it just closes right away install#
I reinstalled pyinstaller using: pip install pyinstaller
Eon timer 2.0 i open it but it just closes right away code#
When I ran my code from the terminal using python my_script.py the program would run fine. I had the same problem as you even though I knew my code wasn't supposed to close immediately since it waited for user_input.
Print("Northern Beaches:", len(NorthernBeaches), "-", round(len(NorthernBeaches)/Total,4), "%") Print("Central Coast:", len(CentralCoast), "-", round(len(CentralCoast)/Total,2), "%") Total = len(CentralCoast) + len(OOR) + len(NorthernBeaches) + len(Invalid) With open('postcodes.txt') as input_file:
0 kommentar(er)
