最新pyinstaller打包python3.6.3完整過程
阿新 • • 發佈：2019-01-05
前言
pyhton3.6.3是目前最新的版本，將python指令碼打包為可執行的exe檔案是通常的需求，這其實是一件比較簡單的事情，但因為python混亂的版本控制和管理，網路上各種臨時方法和補丁滿天飛，應小夥伴的需求再上一篇部落格，把python3.6.3的打包過程完整展現出來。
安裝
pip3 install pyinstaller 即可
注意：別用pip3.6 install
打包
- 進入你要打包的python目錄
- 按照你指令碼程式中檔案需求把python用到的檔案放在一起
- 進入cmd程式醜陋的黑視窗
- 在游標後面鍵入pyinstaller yourfilename.py ，回車即可
- 目錄下出現2個新的目錄：dist、build，build可以刪掉
- 進入dist，找到exe檔案，點選開啟，大功告成！
引數說明
上圖列出pyinstaller的用法示例，常用的如下：
-F 表示生成單個可執行檔案
-w 表示去掉控制檯視窗，這在GUI介面時非常有用。不過如果是命令列程式的話那就把這個選項刪除吧！
-p 表示你自己自定義需要載入的類路徑，一般情況下用不到
-i 表示可執行檔案的圖示
–version-file file_version_info.txt ：表示將標準版本資訊檔案的內容賦給exe檔案的屬性
提醒：如果python需要用到外部的載入檔案，如背景圖片之類，需要按照你的程式中的要求放在相應的目錄下，一般都是拷貝在生成的exe檔案目錄下，python程式中僅用檔名引用就行了，無需路徑。
關於版本資訊的設定問題
方法1：
這是pyinstaller自帶的。
進入C:\Program Files\Python36-32\Lib\site-packages\PyInstaller\utils\cliutils\目錄下，你會看到如下幾個檔案：
其中的grab_version是用來捕獲一個exe檔案的版本資訊並自動在同一目錄下輸出一個file_version_info.txt檔案版本資訊的，其中set_version是用來給一個exe檔案賦值版本資訊的，用法分別如下：
- 進入cmd介面
- 將目錄轉移到C:\Program Files\Python36-32\Lib\site-packages\PyInstaller\utils\cliutils\下
- 拷貝一個要獲取版本資訊的exe檔案到這個目錄下
- 在cmd視窗鍵入：python grab_version.py filename.exe
- 目錄下會自動出現一個標準的file_version_info.txt檔案，雙擊開啟，按照需求修改
- 在cmd視窗鍵入：python set_version.py file_version_info.txt youfilename.exe即可
方法2：
- 在打包的時候就已經準備好了版本資訊檔案：file_version_info.txt
- 打包時附帶有如下引數：pyinstaller –file-version file_version_info.txt yourfile.py即可
方法3
進入
- 進入http://www.carifred.com/fvie/，下載fvie.exe工具，就是file-version-infp-edit的首字母縮寫
- 開啟，選擇你要賦值版本資訊的exe檔案，編輯所需要的資訊，點選確定即可。
這是我成功賦值版本資訊後的樣子
詳細說明
在cmd視窗鍵入：pyinstaller -h就會出現pyinstaller的所用幫助說明，我把詳細內容貼上在這裡，供需要的人學習。
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][-s][--noupx][-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][--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
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.
w to generate:
-d, --debug Tell the bootloader to issue progress messages while
initializing and starting the bundled app. Used to
diagnose problems with missing imports.
-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)Windows and Mac OS X specific options:
-c, --console, --nowindowed
Open a console window for standard i/o (default)
-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. This option is ignored
in *NIX systems.
-i <FILE.ico or FILE.exe,ID or FILE.icns>, --icon <FILE.ico or FILE.exe,ID o
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.