对于PyInstaller生成的可执行文件中的PythonSSL导入错误感兴趣的读者，本文将会是一篇不错的选择，我们将详细介绍python3导入ssl报错，并为您提供关于ManjaroLinux平台用
对于PyInstaller生成的可执行文件中的Python SSL导入错误感兴趣的读者，本文将会是一篇不错的选择，我们将详细介绍python3导入ssl报错，并为您提供关于Manjaro Linux平台用pyinstaller打包python可执行文件、py to exe pyinstaller 导入错误、pyinstaller 把.py文件打包成可执行文件(.exe)、PyInstaller 无法创建可执行文件的有用信息。
本文目录一览：- PyInstaller生成的可执行文件中的Python SSL导入错误（python3导入ssl报错）
- Manjaro Linux平台用pyinstaller打包python可执行文件
- py to exe pyinstaller 导入错误
- pyinstaller 把.py文件打包成可执行文件(.exe)
- PyInstaller 无法创建可执行文件
PyInstaller生成的可执行文件中的Python SSL导入错误（python3导入ssl报错）
我正在尝试分发我创建的Python程序的可执行文件。为此，我正在使用PyInstaller。
我将Windows 7 Professional与Python 3.7配合使用，该程序在PyCharm中运行时会成功运行，并产生预期的结果。
如PyInstaller手册中所述，我使用以下命令创建了dist文件夹：
pyinstaller main.py
日志输出指定该过程成功完成。
尝试main.exe从分发文件夹运行时，会产生以下错误：
Traceback (most recent call last):
File "site-packages\PyInstaller\loader\rthooks\pyi_rth_certifi.py",line 11,i
n <module>
File "c:\users\tim\anaconda3\envs\timtf2_37\lib\site-packages\PyInstaller\load
er\pyimod03_importers.py",line 627,in exec_module
exec(bytecode,module.__dict__)
File "ssl.py",line 98,in <module>
ImportError: DLL load failed: The specified procedure could not be found.
[6236] Failed to execute script pyi_rth_certifi
Manjaro Linux平台用pyinstaller打包python可执行文件
技术背景
当我们创建一个python项目，最终的成果如果希望用户能够不依赖于python源代码也能够正常的执行，就会比较的人性化。因为源代码数量众多，很难让每个用户都自行管理所有的源代码，因此我们需要对源码进行编译构建。对于使用场景不是很复杂的，我们可以直接做成一个可执行文件，这样开发者只需要维护可执行文件的功能正常，以及对于各种平台的兼容性较好，这就可以了。这里我们介绍如何使用pyinstaller去通过python源码构造一个可执行文件。
pyinstaller的安装
我们还是正常的使用pip来进行python包的管理即可：
[dechin@dechin-manjaro installer]$ python3 -m pip install pyinstaller
Collecting pyinstaller
Downloading pyinstaller-4.2.tar.gz (3.6 MB)
|████████████████████████████████| 3.6 MB 18 kB/s
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing wheel Metadata ... done
Collecting pyinstaller-hooks-contrib>=2020.6
Downloading pyinstaller_hooks_contrib-2021.1-py2.py3-none-any.whl (181 kB)
|████████████████████████████████| 181 kB 13 kB/s
Collecting altgraph
Downloading altgraph-0.17-py2.py3-none-any.whl (21 kB)
Requirement already satisfied: setuptools in /home/dechin/anaconda3/lib/python3.8/site-packages (from pyinstaller) (50.3.1.post20201107)
Building wheels for collected packages: pyinstaller
Building wheel for pyinstaller (PEP 517) ... done
Created wheel for pyinstaller: filename=pyinstaller-4.2-py3-none-any.whl size=2413076 sha256=29c4148e9bcda0a6b08f10c1ee3c48f3dd90992787d01b54d1e920b5954f8fd4
Stored in directory: /home/dechin/.cache/pip/wheels/65/6f/54/0f682e8590de992d07a17ce07282267734cb150e537dfc4390
Successfully built pyinstaller
Installing collected packages: pyinstaller-hooks-contrib,altgraph,pyinstaller
Successfully installed altgraph-0.17 pyinstaller-4.2 pyinstaller-hooks-contrib-2021.1
下载安装成功后，可以运行帮助命令来测试一下：
[dechin@dechin-manjaro installer]# pyinstaller -h
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 or "NONE">]
[--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,noarchive},--debug {all,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 or "NONE">,--icon <FILE.ico or FILE.exe,ID or FILE.icns or "NONE">
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. Use "NONE" to not apply any icon,thereby making the OS to show some default (default: apply
PyInstaller's icon)
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.
如果觉得这份官方的帮助文档过于冗余，可以参考下一个章节中的缩略版帮助文档。
构造python测试实例
因为可执行文件的自身内容都是固定的，只能通过配置文件或者是命令行的输入参数来进行传参，因此我们构造python文件的时候主要从命令行的这个角度来出发，通过读取命令行的输入参数来决定python项目的输出。我们这里构造的是一个名为pye的项目，意思是python executable，也就是可执行的python项目，项目的功能是计算一个入参的平方：
# pye.py
import sys
if sys.argv[1] == '-h':
print ('pye: Test the executable python project')
print (' -h')
print ('\t The help message of pye.')
print (' -p2 number')
print ('\t Calculate the power to of input number.')
if sys.argv[1] == '-p2':
print ('The power2 of number {} is : {}'.format(sys.argv[2],float(sys.argv[2]) ** 2))
在上述构造中我们区分了-h和-p2两种参数类型，其中-h是指帮助文档，输出如下所示：
[dechin@dechin-manjaro installer]$ python3 pye.py -h
pye: Test the executable python project
-h
The help message of pye.
-p2 number
Calculate the power to of input number.
而-p2是标识需要计算平方的入参的参数：
[dechin@dechin-manjaro installer]$ python3 pye.py -p2 2
The power2 of number 2 is : 4.0
[dechin@dechin-manjaro installer]$ python3 pye.py -p2 5
The power2 of number 5 is : 25.0
pyinstaller简单示例
由于官方的帮助文档内容太多，不太方便入门，这里我们找了一份简单常用的总结文档（表格来自于参考链接1）：
了解了基本的使用方法之后，可以针对我们上述编写的
pye.py的项目进行编译构建：
[dechin@dechin-manjaro installer]$ pyinstaller -F pye.py --clean
754 INFO: PyInstaller: 4.2
754 INFO: Python: 3.8.5 (conda)
791 INFO: Platform: Linux-5.9.16-1-manjaro-x86_64-with-glibc2.10
791 INFO: wrote /home/dechin/projects/2021-python/installer/pye.spec
794 INFO: UPX is not available.
795 INFO: Removing temporary files and cleaning cache in /home/dechin/.cache/pyinstaller
795 INFO: Extending PYTHONPATH with paths
['/home/dechin/projects/2021-python/installer','/home/dechin/projects/2021-python/installer']
808 INFO: checking Analysis
808 INFO: Building Analysis because Analysis-00.toc is non existent
808 INFO: Initializing module dependency graph...
810 INFO: Caching module graph hooks...
813 WARNING: Several hooks defined for module 'win32ctypes.core'. Please take care they do not conflict.
814 INFO: Analyzing base_library.zip ...
2945 INFO: Processing pre-find module path hook distutils from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks/pre_find_module_path/hook-distutils.py'.
2946 INFO: distutils: retargeting to non-venv dir '/home/dechin/anaconda3/lib/python3.8'
5397 INFO: Caching module dependency graph...
5466 INFO: running Analysis Analysis-00.toc
5487 INFO: Analyzing /home/dechin/projects/2021-python/installer/pye.py
5489 INFO: Processing module hooks...
5489 INFO: Loading module hook 'hook-encodings.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5526 INFO: Loading module hook 'hook-pickle.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5528 INFO: Excluding import of argparse from module pickle
5528 INFO: Loading module hook 'hook-difflib.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5529 INFO: Excluding import of doctest from module difflib
5529 INFO: Loading module hook 'hook-xml.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5600 INFO: Loading module hook 'hook-sysconfig.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5609 INFO: Loading module hook 'hook-_tkinter.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5693 INFO: checking Tree
5693 INFO: Building Tree because Tree-00.toc is non existent
5693 INFO: Building Tree Tree-00.toc
5699 INFO: checking Tree
5699 INFO: Building Tree because Tree-01.toc is non existent
5699 INFO: Building Tree Tree-01.toc
5733 INFO: checking Tree
5733 INFO: Building Tree because Tree-02.toc is non existent
5734 INFO: Building Tree Tree-02.toc
5736 INFO: Loading module hook 'hook-distutils.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5736 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5737 INFO: Loading module hook 'hook-lib2to3.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5757 INFO: Loading module hook 'hook-heapq.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5759 INFO: Excluding import of doctest from module heapq
5759 INFO: Loading module hook 'hook-distutils.util.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5760 INFO: Excluding import of lib2to3.refactor from module distutils.util
5760 INFO: Loading module hook 'hook-multiprocessing.util.py' from '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks'...
5761 INFO: Excluding import of test from module multiprocessing.util
5761 INFO: Excluding import of test.support from module multiprocessing.util
5768 INFO: Looking for ctypes DLLs
5791 INFO: Analyzing run-time hooks ...
5794 INFO: Including run-time hook '/home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/hooks/rthooks/pyi_rth_multiprocessing.py'
5799 INFO: Looking for dynamic libraries
6299 INFO: Looking for eggs
6300 INFO: Python library not in binary dependencies. Doing additional searching...
6315 INFO: Using Python library /home/dechin/anaconda3/lib/libpython3.8.so.1.0
6321 INFO: Warnings written to /home/dechin/projects/2021-python/installer/build/pye/warn-pye.txt
6352 INFO: Graph cross-reference written to /home/dechin/projects/2021-python/installer/build/pye/xref-pye.html
6361 INFO: checking PYZ
6361 INFO: Building PYZ because PYZ-00.toc is non existent
6361 INFO: Building PYZ (ZlibArchive) /home/dechin/projects/2021-python/installer/build/pye/PYZ-00.pyz
6647 INFO: Building PYZ (ZlibArchive) /home/dechin/projects/2021-python/installer/build/pye/PYZ-00.pyz completed successfully.
6649 INFO: checking PKG
6650 INFO: Building PKG because PKG-00.toc is non existent
6650 INFO: Building PKG (CArchive) PKG-00.pkg
10882 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
10883 INFO: Bootloader /home/dechin/anaconda3/lib/python3.8/site-packages/PyInstaller/bootloader/Linux-64bit/run
10883 INFO: checking EXE
10884 INFO: Building EXE because EXE-00.toc is non existent
10884 INFO: Building EXE from EXE-00.toc
10884 INFO: Appending archive to ELF section in EXE /home/dechin/projects/2021-python/installer/dist/pye
10914 INFO: Building EXE from EXE-00.toc completed successfully.
执行成功编译构建的方法之后，会在本地产生一些编译的路径，如build和dist等，完整的路径和文件清单如下所示：
[dechin@dechin-manjaro installer]$ tree
.
├── build
│ └── pye
│ ├── Analysis-00.toc
│ ├── base_library.zip
│ ├── EXE-00.toc
│ ├── PKG-00.pkg
│ ├── PKG-00.toc
│ ├── PYZ-00.pyz
│ ├── PYZ-00.toc
│ ├── Tree-00.toc
│ ├── Tree-01.toc
│ ├── Tree-02.toc
│ ├── warn-pye.txt
│ └── xref-pye.html
├── dist
│ └── pye
├── __pycache__
│ └── pye.cpython-38.pyc
├── pye.py
└── pye.spec
4 directories,16 files
我们可以看到在dist目录下有一个单独的可执行文件，这个就是我们最终想要的文件了。我们可以在dist目录下执行运行这个文件：
[dechin@dechin-manjaro dist]$ ./pye -h
pye: Test the executable python project
-h
The help message of pye.
-p2 number
Calculate the power to of input number.
[dechin@dechin-manjaro dist]$ ./pye -p2 5
The power2 of number 5 is : 25.0
经过验证所有的功能都正常。那么最后还缺一步，就是我们如果想要通过项目名 -参数表示 参数这样的方法来运行我们的项目的话，就需要把这个可执行文件添加到系统路径中。最常用的方法其实是直接将该可执行文件拷贝到/usr/bin/目录下，这样该可执行文件就可以直接使用，不需要在前面加上路径就能运行。当然，为了执行这个操作，我们首先需要切换到root帐号下，再执行文件拷贝操作：
[dechin-root dist]# cp pye /usr/bin/
拷贝完成后，直接运行：
[dechin-root dist]# pye -h
pye: Test the executable python project
-h
The help message of pye.
-p2 number
Calculate the power to of input number.
[dechin-root installer]# pye -p2 7
The power2 of number 7 is : 49.0
我们发现所有的功能都是正常的，并且在普通帐号下也是可以正常使用的。到这里为止，我们就达到了项目所预期的效果。
总结概要
通过pyinstaller我们可以将一个python项目打包编译构建成一个可执行文件，然后将该可执行文件放置到一个系统路径下，使得系统可以不需要路径也能够识别到这个可执行文件，这样我们就可以仅配置一些输入文件或者命令行的入参，来运行我们的项目。
版权声明
本文首发链接为：https://www.cnblogs.com/dechinphy/p/pyinstaller.html
作者ID：DechinPhy
更多原著文章请参考：https://www.cnblogs.com/dechinphy/
参考链接
- https://www.jianshu.com/p/825397df4aa0
py to exe pyinstaller 导入错误
如何解决py to exe pyinstaller 导入错误？
我正在尝试使用 pyinstaller 将单个文件 python 脚本/项目转换为 exe
甚至认为 pyinstaller 会转换脚本 .exe 将运行并抛出这个
Traceback (most recent call last):
File "main.py",line 4,in <module>
File "PyInstaller\loader\pyimod03_importers.py",line 540,in exec_module
File "pynput\__init__.py",line 40,in exec_module
File "pynput\keyboard\__init__.py",line 31,in <module>
File "pynput\_util\__init__.py",line 76,in backend
ImportError
[16676] Failed to execute script main
我很难过，通过我的反复试验，我发现当我用像 random
这样的模块替换 pynput 时，转换工作正常，但我需要它与 pynput
一起使用
请帮忙，提前致谢！
解决方法
作者做了一些改动，我觉得这打破了参考。
所以它不是打包而是引用文件。
- backend = backend(__package__)
+ backend = backend(__name__)
请尝试降级您的软件包并检查您的应用是否仍然有效。
pip install pynput==1.6.8
然后您的命令如下所示。
pyinstaller --onefile build_pkg_for.py
pyinstaller 把.py文件打包成可执行文件(.exe)
pyinstaller 是一个很有用的第三方库，通过对源文件打包，让我们的python文件可以跨系统跨环境运行。
前言
给小姐姐写了个python文件，功能实现了，但怎么给她呢。两种方案：
- 直接给python文件，然后让她自行安装python。
- 把python文件和python环境一起给她，她直接点点点即可。
本着码农懒懒懒的精神，方案一不予通过， 采用方案二。
pyinstaller
pyinstaller 可以把python文件直接打包成可执行文件，符合需求。
安装
- 如果你的python不是3.8.0，应该可以这样安装，如果你的python版本是3.8.0，可以跳到文章末尾看安装方式
pip install pyinstaller如果一直报超时错误，如下，
可以这样安装
pip install pyinstaller --trusted-host https://pypi.org --trusted-host https://files.pythonhosted.org安装成功，查看pyinstaller版本验证pyinstaller是否成功
pyinstaller --version
3.5如果正常输出pyinstaller版本说明安装成功
打包
# -F 指的是打包成一个文件
pyinstaller -F xxx.py如果执行成功，并且dist文件夹下的xxx.exe可以正常运行，那么恭喜你，打包成功了。如果打包时报如下错误
那很可能是版本不对，可以试试如下安装pyinstaller
pip install https://github.com/pyinstaller/pyinstaller/archive/develop.tar.gz我的python是3.8.0，报了这个错，原因如下
打包成功，执行
打包成功之后，你会看到多出了几个新的文件，不要害怕，不要凌乱。打开dist文件夹，你需要的可执行文件就在这里。点点点即可。
Oh, No. 点点点，可以看见文件确实执行了，但是没有报错也没有输出预期结果，反正我是有一点凌乱了。
看官网梳理流程，确定应该没有错误。预估可能原因：
- 使用了第三方库，但是打包并没有报错。无从下手
- 源文件出问题
python xxxx.py
// 报错
"XXXXXX"找不到（类似）之前运行是没有错误的，不知道为什么突然又没有这个库，后来仔细想了想，应该是我之前用的python2安装的，今天打包用的是python3。
此时想到一句话，论挖坑技术哪家强，~
重新安装，打包，执行。
完美。
附上部分打包命令：
pyinstaller API Document
往期文章：
python批量修改excel文件——xlrd、xlutils
python批量修改excel文件 xlwings
我的python学习笔记
最后
欢迎一起快乐的挖坑、填坑，哈哈哈
PyInstaller 无法创建可执行文件
如何解决PyInstaller 无法创建可执行文件？
希望你们一切顺利。我在 Kivy 中开发了一个用于位置跟踪的 Python 脚本。现在我需要把这个脚本变成一个可执行文件（不需要一个文件的可执行文件；一个文件夹包就足够了）。我尝试了 here 概述的步骤。我先给你看看我的文件内容；然后是我在整个过程中完成的步骤：
.kv 文件
MapView:
id: map_view
zoom: 17
lat: app.latitude
lon: app.longitude
MapMarker:
id: map_view_marker
lat: app.latitude
lon: app.longitude
.py 文件（只是导入的模块）
#!/usr/bin/env python
# -*- coding: utf-8 -*-
from datetime import datetime
from kivy.lang import Builder
from kivy.app import App
from kivy.properties import StringProperty
from kivy.uix.Boxlayout import BoxLayout
from kivy.clock import Clock
from kivy.garden.mapview import MapView,MapMarker
import MysqL.connector
import os
我使用了虚拟环境来开发脚本，因此我从虚拟环境命令窗口 (Windows CMD) 中使用了 PyInstaller。这是我使用的第一个命令：
python -m PyInstaller --name pika mapview_try.py
之后，我修改了如下创建的 .spec 文件：
.spec 文件：
from kivy_deps import sdl2,glew
# -*- mode: python ; coding: utf-8 -*-
block_cipher = None
a = Analysis([''mapview_try.py''],pathex=[''C:\\Users\\Lenovo\\Desktop\\Bizero\\pika_Takip''],binaries=[],datas=[],hiddenimports=[''kivy''],hookspath=[],runtime_hooks=[],excludes=[],win_no_prefer_redirects=False,win_private_assemblies=False,cipher=block_cipher,noarchive=False)
pyz = PYZ(a.pure,a.zipped_data,cipher=block_cipher)
a.datas += [(''Code\mapview_try.kv'',''C:\\Users\\Lenovo\\Desktop\\Bizero\\pika_Takip\mapview_try.kv'',''DATA'')]
exe = EXE(pyz,a.scripts,[],exclude_binaries=True,name=''mapview_try'',debug=False,bootloader_ignore_signals=False,strip=False,upx=True,console=False )
coll = COLLECT(exe,Tree(''C:\\Users\\Lenovo\\Desktop\\Bizero\\pika_Takip\\''),a.binaries,a.zipfiles,a.datas,*[Tree(p) for p in (sdl2.dep_bins + glew.dep_bins)],upx_exclude=[],name=''mapview_try'')
之后，我在同一个 cmd 窗口中运行以下命令：
python -m PyInstaller pika.spec
但是，当我尝试在此命令之后运行可执行文件时。我收到“kivy.garden”未找到错误。我可以找到这个模块的目录并直接添加到可执行文件的路径中吗？或者是否有我可以用来导入所有模块的命令参数？提前致谢。
解决方法
暂无找到可以解决该程序问题的有效方法，小编努力寻找整理中！
如果你已经找到好的解决方法，欢迎将解决方案带上本链接一起发送给小编。
小编邮箱:dio#foxmail.com (将#修改为@）
今天关于PyInstaller生成的可执行文件中的Python SSL导入错误和python3导入ssl报错的介绍到此结束，谢谢您的阅读，有关Manjaro Linux平台用pyinstaller打包python可执行文件、py to exe pyinstaller 导入错误、pyinstaller 把.py文件打包成可执行文件(.exe)、PyInstaller 无法创建可执行文件等更多相关知识的信息可以在本站进行查询。
本文标签：
