# Display an icon on the executable file, this option is only valid for windows and mac # On Windows this option has no effect if the first script is a ‘.pyw’ file. # Open a console window for standard i/o (default). # This option is ignored in *NIX systems. # On Windows this option will be set if the first script is a ‘.pyw’ file. # On Mac OS X this also triggers building an OS X. # Do not provide a console window for standard i/o. # Create a one-folder bundle containing an executable (default) Here are some example with common options: If you want your executable to run without external files as dependencies, you can pack everythin into one file: Generate a executabl according to `main.spec` Create `./dist/`, where your executable and bundle apps located. Create `./build/`, where logging and middle biniary files located. Excute following with administration access: If `pip` is not available in your enviroment, then you can download the archive and unzip it. In this note, I will also show you the basic, the simplest way to pack your executable and I will also show you how to deal with the annoying import errors. However, most of them just show one or two command packing the executable in the simplest way.

There are a bunch of tutorials showing how to pack your `.py` code to an executable(such as `.exe` in windows). # Python `.py` to `.exe` using `pyinstaller`

Pyinstaller windows