bod-idv-tw小書製作: Python : 使用PyInstaller把專案程式打包封裝成EXE執行檔

安裝PyInstaller：
(base) C:\ProgramData\Anaconda3>pip install PyInstaller
Collecting PyInstaller
Downloading https://files.pythonhosted.org/packages/e2/c9/0b44b2ea87ba36395483a672fddd07e6a9cb2b8d3c4a28d7ae76c7e7e1e5/PyInstaller-3.5.tar.gz (3.5MB)
|████████████████████████████████| 3.5MB 3.3MB/s
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing wheel metadata ... done
Collecting pywin32-ctypes>=0.2.0 (from PyInstaller)
Downloading https://files.pythonhosted.org/packages/9e/4b/3ab2720f1fa4b4bc924ef1932b842edf10007e4547ea8157b0b9fc78599a/pywin32_ctypes-0.2.0-py2.py3-none-any.whl
Collecting pefile>=2017.8.1 (from PyInstaller)
Downloading https://files.pythonhosted.org/packages/36/58/acf7f35859d541985f0a6ea3c34baaefbfaee23642cf11e85fe36453ae77/pefile-2019.4.18.tar.gz (62kB)
|████████████████████████████████| 71kB 2.3MB/s
Requirement already satisfied: setuptools in c:\programdata\anaconda3\lib\site-packages (from PyInstaller) (41.0.1)
Collecting altgraph (from PyInstaller)
Downloading https://files.pythonhosted.org/packages/0a/cc/646187eac4b797069e2e6b736f14cdef85dbe405c9bfc7803ef36e4f62ef/altgraph-0.16.1-py2.py3-none-any.whl
Requirement already satisfied: future in c:\programdata\anaconda3\lib\site-packages (from pefile>=2017.8.1->PyInstaller) (0.17.1)
Building wheels for collected packages: PyInstaller
Building wheel for PyInstaller (PEP 517) ... done
Stored in directory: C:\Users\Hannibal\AppData\Local\pip\Cache\wheels\c6\a4\e0\d9a1c5d3d876eb0675171281c293aed80839115e2eb022e6d2
Successfully built PyInstaller
Building wheels for collected packages: pefile
Building wheel for pefile (setup.py) ... done
Stored in directory: C:\Users\Hannibal\AppData\Local\pip\Cache\wheels\1c\a1\95\4f33011a0c013c872fe6f0f364dc463a2588120820e40a30d8
Successfully built pefile
Installing collected packages: pywin32-ctypes, pefile, altgraph, PyInstaller
Successfully installed PyInstaller-3.5 altgraph-0.16.1 pefile-2019.4.18 pywin32-ctypes-0.2.0
PyInstaller的參數：
(base) C:\ProgramData\Anaconda3\Scripts>PyInstaller --help
usage: pyinstaller [-h] [-v] [-D] [-F] [--specpath DIR] [-n NAME]
[--add-data <SRC;DEST or SRC:DEST>]
[--add-binary <SRC;DEST or SRC:DEST>] [-p DIR]
[--hidden-import MODULENAME]
[--additional-hooks-dir HOOKSPATH]
[--runtime-hook RUNTIME_HOOKS] [--exclude-module EXCLUDES]
[--key KEY] [-d {all,imports,bootloader,noarchive}] [-s]
[--noupx] [--upx-exclude FILE] [-c] [-w]
[-i <FILE.ico or FILE.exe,ID or FILE.icns>]
[--version-file FILE] [-m <FILE or XML>] [-r RESOURCE]
[--uac-admin] [--uac-uiaccess] [--win-private-assemblies]
[--win-no-prefer-redirects]
[--osx-bundle-identifier BUNDLE_IDENTIFIER]
[--runtime-tmpdir PATH] [--bootloader-ignore-signals]
[--distpath DIR] [--workpath WORKPATH] [-y]
[--upx-dir UPX_DIR] [-a] [--clean] [--log-level LEVEL]
scriptname [scriptname ...]

positional arguments:
scriptname name of scriptfiles to be processed or exactly one
.spec-file. If a .spec-file is specified, most options
are unnecessary and are ignored.

optional arguments:
-h, --help show this help message and exit
-v, --version Show program version info and exit.
--distpath DIR Where to put the bundled app (default: .\dist)
--workpath WORKPATH Where to put all the temporary work files, .log, .pyz
and etc. (default: .\build)
-y, --noconfirm Replace output directory (default:
SPECPATH\dist\SPECNAME) without asking for confirmation
--upx-dir UPX_DIR Path to UPX utility (default: search the execution path)
-a, --ascii Do not include unicode encoding support (default:included if available)
--clean Clean PyInstaller cache and remove temporary files before building.
--log-level LEVEL Amount of detail in build-time console messages. LEVEL
may be one of TRACE, DEBUG, INFO, WARN, ERROR,
CRITICAL (default: INFO).

What to generate:
-D, --onedir Create a one-folder bundle containing an executable (default)
-F, --onefile Create a one-file bundled executable.
--specpath DIR Folder to store the generated spec file (default: current directory)
-n NAME, --name NAME Name to assign to the bundled app and spec file
(default: first script's basename)

What to bundle, where to search:
--add-data <SRC;DEST or SRC:DEST>
Additional non-binary files or folders to be added to
the executable. The path separator is platform
specific, ``os.pathsep`` (which is ``;`` on Windows
and ``:`` on most unix systems) is used. This option
can be used multiple times.
--add-binary <SRC;DEST or SRC:DEST>
Additional binary files to be added to the executable.
See the ``--add-data`` option for more details. This
option can be used multiple times.
-p DIR, --paths DIR A path to search for imports (like using PYTHONPATH).
Multiple paths are allowed, separated by ';', or use
this option multiple times
--hidden-import MODULENAME, --hiddenimport MODULENAME
Name an import not visible in the code of the
script(s). This option can be used multiple times.
--additional-hooks-dir HOOKSPATH
An additional path to search for hooks. This option
can be used multiple times.
--runtime-hook RUNTIME_HOOKS
Path to a custom runtime hook file. A runtime hook is
code that is bundled with the executable and is
executed before any other code or module to set up
special features of the runtime environment. This
option can be used multiple times.
--exclude-module EXCLUDES
Optional module or package (the Python name, not the
path name) that will be ignored (as though it was not
found). This option can be used multiple times.
--key KEY The key used to encrypt Python bytecode.

How to generate:
-d {all,imports,bootloader,noarchive}, --debug {all,imports,bootloader,noarchive}
Provide assistance with debugging a frozen
application. This argument may be provided multiple
times to select several of the following options.
- all: All three of the following options.
- imports: specify the -v option to the underlying
Python interpreter, causing it to print a message
each time a module is initialized, showing the
place (filename or built-in module) from which it
is loaded. See
https://docs.python.org/3/using/cmdline.html#id4.
- bootloader: tell the bootloader to issue progress
messages while initializing and starting the
bundled app. Used to diagnose problems with
missing imports.
- noarchive: instead of storing all frozen Python
source files as an archive inside the resulting
executable, store them as files in the resulting
output directory.
-s, --strip Apply a symbol-table strip to the executable and
shared libs (not recommended for Windows)
--noupx Do not use UPX even if it is available (works
differently between Windows and *nix)
--upx-exclude FILE Prevent a binary from being compressed when using upx.
This is typically used if upx corrupts certain
binaries during compression. FILE is the filename of
the binary without path. This option can be used
multiple times.

Windows and Mac OS X specific options:
-c, --console, --nowindowed
Open a console window for standard i/o (default). On
Windows this option will have no effect if the first
script is a '.pyw' file.
-w, --windowed, --noconsole
Windows and Mac OS X: do not provide a console window
for standard i/o. On Mac OS X this also triggers
building an OS X .app bundle. On Windows this option
will be set if the first script is a '.pyw' file. This
option is ignored in *NIX systems.
-i <FILE.ico or FILE.exe,ID or FILE.icns>, --icon <FILE.ico or FILE.exe,ID or FILE.icns>
FILE.ico: apply that icon to a Windows executable.
FILE.exe,ID, extract the icon with ID from an exe.
FILE.icns: apply the icon to the .app bundle on Mac OS X

Windows specific options:
--version-file FILE add a version resource from FILE to the exe
-m <FILE or XML>, --manifest <FILE or XML>
add manifest FILE or XML to the exe
-r RESOURCE, --resource RESOURCE
Add or update a resource to a Windows executable. The
RESOURCE is one to four items,
FILE[,TYPE[,NAME[,LANGUAGE]]]. FILE can be a data file
or an exe/dll. For data files, at least TYPE and NAME
must be specified. LANGUAGE defaults to 0 or may be
specified as wildcard * to update all resources of the
given TYPE and NAME. For exe/dll files, all resources
from FILE will be added/updated to the final
executable if TYPE, NAME and LANGUAGE are omitted or
specified as wildcard *.This option can be used
multiple times.
--uac-admin Using this option creates a Manifest which will
request elevation upon application restart.
--uac-uiaccess Using this option allows an elevated application to
work with Remote Desktop.

Windows Side-by-side Assembly searching options (advanced):
--win-private-assemblies
Any Shared Assemblies bundled into the application
will be changed into Private Assemblies. This means
the exact versions of these assemblies will always be
used, and any newer versions installed on user
machines at the system level will be ignored.
--win-no-prefer-redirects
While searching for Shared or Private Assemblies to
bundle into the application, PyInstaller will prefer
not to follow policies that redirect to newer
versions, and will try to bundle the exact versions of
the assembly.

Mac OS X specific options:
--osx-bundle-identifier BUNDLE_IDENTIFIER
Mac OS X .app bundle identifier is used as the default
unique program name for code signing purposes. The
usual form is a hierarchical name in reverse DNS
notation. For example:
com.mycompany.department.appname (default: first
script's basename)

Rarely used special options:
--runtime-tmpdir PATH
Where to extract libraries and support files in
`onefile`-mode. If this option is given, the
bootloader will ignore any temp-folder location
defined by the run-time OS. The ``_MEIxxxxxx``-folder
will be created here. Please use this option only if
you know what you are doing.
--bootloader-ignore-signals
Tell the bootloader to ignore signals rather than
forwarding them to the child process. Useful in
situations where e.g. a supervisor process signals
both the bootloader and child (e.g. via a process
group) to avoid signalling the child twice.
打包封裝的範例
PyInstaller -F -w --key "TheKeyUsedToEncryptPythonBytecode" CallWeatherWin.py
-F:打包封裝成一個執行檔 (-D:打包封裝成一個目錄)
-w:這是一個視窗程式(window)，不是主控台程式(console)
--key:程式碼封裝加密的金鑰
打包封裝的結果放在dist目錄內。打包的執行檔只能在原相同作業系統下執行(64位元/32位元是有區分的)

D:\MyWorkSpaces\VSWorks\ch10a\weather2>PyInstaller -F -w --key "TheKeyUsedToEncryptPythonBytecode" CallWeatherWin.py
159 INFO: PyInstaller: 3.5
164 INFO: Python: 3.7.3
167 INFO: Platform: Windows-10-10.0.18362-SP0
179 INFO: wrote D:\MyWorkSpaces\VSWorks\ch10a\weather2\CallWeatherWin.spec
181 INFO: UPX is not available.
212 INFO: Extending PYTHONPATH with paths
['D:\\MyWorkSpaces\\VSWorks\\ch10a\\weather2',
'D:\\MyWorkSpaces\\VSWorks\\ch10a\\weather2']
212 INFO: Will encrypt Python bytecode with key: TheKeyUsedToEncr
221 INFO: Adding dependencies on pyi_crypto.py module
223 INFO: checking Analysis
223 INFO: Building Analysis because Analysis-00.toc is non existent
224 INFO: Initializing module dependency graph...
236 INFO: Initializing module graph hooks...
251 INFO: Analyzing base_library.zip ...
13714 INFO: Analyzing hidden import 'Crypto.Cipher._AES'
14066 INFO: running Analysis Analysis-00.toc
14107 INFO: Adding Microsoft.Windows.Common-Controls to dependent assemblies of final executable
required by c:\programdata\anaconda3\python.exe
14779 INFO: Caching module hooks...
14811 INFO: Analyzing D:\MyWorkSpaces\VSWorks\ch10a\weather2\CallWeatherWin.py
16113 INFO: Processing pre-safe import module hook urllib3.packages.six.moves
20871 INFO: Processing pre-safe import module hook six.moves
25919 INFO: Loading module hooks...
25920 INFO: Loading module hook "hook-certifi.py"...
25927 INFO: Loading module hook "hook-Crypto.py"...
Traceback (most recent call last):
File "", line 2, in
ModuleNotFoundError: No module named 'Crypto.Math'
26049 INFO: Loading module hook "hook-cryptography.py"...
26814 INFO: Loading module hook "hook-encodings.py"...
26983 INFO: Loading module hook "hook-pydoc.py"...
26987 INFO: Loading module hook "hook-PyQt5.py"...
27509 INFO: Loading module hook "hook-PyQt5.QtCore.py"...
27678 INFO: Loading module hook "hook-PyQt5.QtGui.py"...
28090 INFO: Loading module hook "hook-PyQt5.QtWidgets.py"...
28761 INFO: Loading module hook "hook-xml.py"...
29119 INFO: Looking for ctypes DLLs
29157 INFO: Analyzing run-time hooks ...
29165 INFO: Including run-time hook 'pyi_rth_certifi.py'
29177 INFO: Including run-time hook 'pyi_rth_pyqt5.py'
29202 INFO: Looking for dynamic libraries
32584 INFO: Looking for eggs
32585 INFO: Using Python library c:\programdata\anaconda3\python37.dll
32586 INFO: Found binding redirects:
[]
32606 INFO: Warnings written to D:\MyWorkSpaces\VSWorks\ch10a\weather2\build\CallWeatherWin\warn-CallWeatherWin.txt
32762 INFO: Graph cross-reference written to D:\MyWorkSpaces\VSWorks\ch10a\weather2\build\CallWeatherWin\xref-CallWeatherWin.html
32848 INFO: checking PYZ
32848 INFO: Building PYZ because PYZ-00.toc is non existent
32850 INFO: Building PYZ (ZlibArchive) D:\MyWorkSpaces\VSWorks\ch10a\weather2\build\CallWeatherWin\PYZ-00.pyz
34987 INFO: Building PYZ (ZlibArchive) D:\MyWorkSpaces\VSWorks\ch10a\weather2\build\CallWeatherWin\PYZ-00.pyz completed successfully.
35048 INFO: checking PKG
35050 INFO: Building PKG because PKG-00.toc is non existent
35050 INFO: Building PKG (CArchive) PKG-00.pkg
35731 WARNING: One binary added with two internal names.
35732 WARNING: ('libGLESv2.dll',
'C:\\programdata\\anaconda3\\lib\\site-packages\\PyQt5\\Qt\\bin\\libGLESv2.dll',
'BINARY')
35733 WARNING: was placed previously at
35735 WARNING: ('PyQt5\\Qt\\bin\\libGLESv2.dll',
'C:\\programdata\\anaconda3\\lib\\site-packages\\PyQt5\\Qt\\bin\\libGLESv2.dll',
'BINARY')
60664 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
60689 INFO: Bootloader c:\programdata\anaconda3\lib\site-packages\PyInstaller\bootloader\Windows-64bit\runw.exe
60690 INFO: checking EXE
60691 INFO: Building EXE because EXE-00.toc is non existent
60693 INFO: Building EXE from EXE-00.toc
60696 INFO: Appending archive to EXE D:\MyWorkSpaces\VSWorks\ch10a\weather2\dist\CallWeatherWin.exe
61113 INFO: Building EXE from EXE-00.toc completed successfully.