hello there!
First, congratulations for plucking up the courage to use python, I respect you right away.
Second, lets talk about pyinstaller, your new best friend.
First things first, don't compile your program into a .exe file until you know it works.
So, instead of running pyinstaller myprogram.py
run: python mypogram.py
this will tell you all of the problems you have.
Done that already? Fantastic!
Lets talk about a few things about pyinstaller. Here is what I use to compile my python programs:
1, if its in development:
pyinstaller program.py --onefile
2. If its not:
pyinstaller program.py --onefile --windowed.
But what does this mean?
--onefile: this means compress my project into one file only.
--windowed: This means make sure that, when the program is run, the python window is hidden.
So, why exclude off windowed when in development?
Because then you can run your pyinstaller, then do cd dist, and then program.exe
that way, if your program freezes, tracebacks or errors, you can see why it did and what the problem is.
GOOD TIMES!
A note about certain modules:
Certain modules, such as accessible_output2, and sound_lib may require you to copy them into the dist folder, I recently discovered a way in which you can write it into the specfile to make it compile them in, but that's a story for another day.
Hope this helps, and my pm/email is open to further assistance if you so need.
My greatest respect for using python
Nathan Smith
Managing Director of Nathan Tech
It's not disability
It's ability!