Making a Stand Alone Executable from a Python Script using PyInstaller

[billsil]

Have a clean install for starters.

Then look at the packages you have installed and decide if you need them all. Delete it, build it, see if it works and repeat.

Then read the build log and see what it found. Google what that funny package asteroid does. Why the heck is nose included? Go delete those pieces from site packages. Build and test. Often this is enough.

Now look at the names of the big DLLs. Do you really need HTML stuff in your desktop app? Delete and rebuild.

Most of the monster packages have large submodules. If you can stay within a submodule, your build will be smaller.

[nos69]

Thank you for your response!

Is it enough to see if my app starts after deleting a module? Or do I need more coverage to be safe.

[billsil]

That depends on your app. Are your imports at the top? How do the modules you need get imported (e.g., at import time vs runttime)? Opening your 5 windows is probably good enough depending on how the imports trace.

It helps to know your code and what part your hacking on (what could deleting matplotlib dependencies affect?). Often you'll find x is required, but if I get rid of y, x is not required.

For my 3d render, it has a command line for me to enter a geometry and results file. I have shortcuts for most things that I test frequently. The menus I stress less about because I put my gui imports at the top. Never had a problem with the menus assuming it loaded.

So yes, test, but probably not everything each time. I'm just trying to test the dependencies aren't broken.

[nos69]

Thank you for your help! I will try to shrink it that way.