python 程序双击执行的小技巧

文章更新于：2020-04-03

按照惯例，需要的文件附上链接放在文首。

文件名：ICOFX图标制作软件.7z

文件大小：40.2 MB

下载链接：https://www.lanzous.com/iayxw2b

SHA256: 76661654826A23DD4D5AEC466E4E775FD593DF7289587FD4B093AE345E22DE21

点击目录可跳转

一、使用 PyInstaller 打包程序

1.1、可以使用 pip 进行安装
1.2、执行打包命令
1.3、查看程序文件
1.4、引入文件

二、如何减少打包体积

2.1、改善 import 语句
2.2、使用 pipenv
2.3 PyInstaller 命令参数：

三、Enjoy！

一、使用 PyInstaller 打包程序

1.1、可以使用 pip 进行安装

pip install PyInstaller

# 如果出现 success 标志即安装成功

1.2、执行打包命令

在 py文件所在文件夹地址栏输入 cmd 回车进入命令行，输入 pyinstaller -F name.py 进行打包。

pyinstall -F --icon ok.ico 程序文件名.py

其中 -F 参数表示将程序打包成一个独立的文件。

如果你想自定义图标的话，你可以使用 --icon 参数。

注：这个 icon 文件需要是 ico 文件，如果你只是把图片改个后缀，它应该是会报错的。

如何制作 icon 文件，可以参见文首的链接。

1.3、查看程序文件

打包完成之后就可以去当前目录 dist 文件夹查看程序文件了。

这个程序文件理论上双击即可执行~

1.4、引入文件

如果你的程序引入了其他文件，比如一个 txt 文件，那么如果你想把其也打包进去，你就需要修改中间文件spec 配置文件。

在打包时生成的 spec 文件中，找到 datas 文件，添加一个元祖。

datas=[(‘res’, ’.’)] 第一项为资源文件所在的文件夹，第二个值‘.’代表当前路径。

之后再次 pyinstall -F xxx.spec打包即可。

这时文件即可正常打包进程序。

二、如何减少打包体积

我们会发现，使用其打包以后，程序的体积往往远大于源代码的体积。

这是因为其可能引入了一些不必要的文件。

为了减少体积，我们可以这样：

2.1、改善 import 语句

能用 from xxx import xxx 就不用 import xxx ，前者更轻量！

2.2、使用 pipenv

使用 pipenv 建立虚拟环境，然后安装程序引入的包以后再进行打包，可以进一步减小程序的体积。

具体操作是：

#建立虚拟环境（也可直接执行第二步）

pipenv install

#进入虚拟环境

pipenv shell

#安装你程序引入的库文件

pip install xxx

#安装打包库文件

pip install pyinstaller

#开始打包

pyinstaller -F -i ok.ico  程序名.py

2.3 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 {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.

三、Enjoy！