最新pyinstaller打包python3.6.3完整过程

前言
pyhton3.6.3是目前最新的版本，将python脚本打包为可执行的exe文件是通常的需求，这其实是一件比较简单的事情，但因为python混乱的版本控制和管理，网络上各种临时方法和补丁满天飞，应小伙伴的需求再上一篇博客，把python3.6.3的打包过程完整展现出来。

安装
pip3 install pyinstaller 即可
注意：别用pip3.6 install

打包

1. 进入你要打包的python目录
2. 按照你脚本程序中文件需求把python用到的文件放在一起
3. 进入cmd程序丑陋的黑窗口
4. 在光标后面键入pyinstaller yourfilename.py ，回车即可
5. 目录下出现2个新的目录：dist、build，build可以删掉
6. 进入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文件赋值版本信息的，用法分别如下：

1. 进入cmd界面
2. 将目录转移到C:\Program Files\Python36-32\Lib\site-packages\PyInstaller\utils\cliutils\下
3. 拷贝一个要获取版本信息的exe文件到这个目录下
4. 在cmd窗口键入：python grab_version.py filename.exe
5. 目录下会自动出现一个标准的file_version_info.txt文件，双击打开，按照需求修改
6. 在cmd窗口键入：python set_version.py file_version_info.txt youfilename.exe即可

方法2：

1. 在打包的时候就已经准备好了版本信息文件：file_version_info.txt
2. 打包时附带有如下参数：pyinstaller –file-version file_version_info.txt yourfile.py即可

方法3

进入

1. 进入http://www.carifred.com/fvie/，下载fvie.exe工具，就是file-version-infp-edit的首字母缩写
   
2. 打开，选择你要赋值版本信息的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 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 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 or FILE.exe,ID or FILE.icns>, --icon 
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 or XML>, --manifest 
                        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.