一、環境搭建：
1、Pycharm開發工具
pycharm歷史版本 https://www.jetbrains.com/pycharm/download/other.html 破解外掛 https://blog.csdn.net/weixin_50737119/article/details/135628513
2、PYENV 版本管理
Python也有對應的版本管理工具，叫pyenv
這個東西挺奇怪的，直接釋出的原始碼，不是安裝包
https://github.com/pyenv-win/pyenv-win/releases
環境變數直接繫結到bin目錄下，會發現pyenv會推薦讓你配置這三個變數
C:\Users\Administrator>pyenv --version PYENV variable is not set, recommended to set the variable. PYENV_ROOT variable is not set, recommended to set the variable. PYENV_HOME variable is not set, recommended to set the variable. pyenv 3.1.1
其實配置第一個就可以了
系統變數新建一個KV對的變數，Key值為 PYENV D:\pyenv-win-3.1.1\pyenv-win 然後在系統變數Path中追加 %PYENV%\bin
%PYENV%\shims
預設的映象源提供的版本有限，這裡參考知乎的部落格：
https://zhuanlan.zhihu.com/p/597559112
windows配置pyenv映象源：
系統變數新建一個kv對變數，key值為 PYTHON_BUILD_MIRROR_URL https://jedore.netlify.app/tools/python-mirrors/
2-1、Python本體下載
要是不需要頻繁切換版本，可以直接下載本體就好了
https://www.python.org/downloads/
3、GUI開發庫支援
安裝python後使用pip包管理工具下載
pip install PyQt6 -i https://pypi.tuna.tsinghua.edu.cn/simple/ pip install PyQt6-tools -i https://pypi.tuna.tsinghua.edu.cn/simple/
如果清華映象源不行（聯通網無法連線教育網導致），改用其他源，或者不使用
http://mirrors.aliyun.com/pypi/simple/ http://pypi.mirrors.ustc.edu.cn/simple/ http://pypi.douban.com/simple/
3-1、打包工具庫
pip install pyinstaller -i https://pypi.tuna.tsinghua.edu.cn/simple/
4、配置PyQT和Pycharm的互動
https://blog.csdn.net/pyscl01/article/details/131522183/
五、原始碼打包
打包成可執行檔案exe
需要pyinstalller庫的支援，先看命令有什麼
C:\Users\Administrator\PycharmProjects\pythonProject> pyinstaller -h
usage: pyinstaller [-h] [-v] [-D] [-F] [--specpath DIR] [-n NAME] [--contents-directory CONTENTS_DIRECTORY] [--add-data SOURCE:DEST]
[--add-binary SOURCE:DEST] [-p DIR] [--hidden-import MODULENAME] [--collect-submodules MODULENAME] [--collect-data MODULENAME]
[--collect-binaries MODULENAME] [--collect-all MODULENAME] [--copy-metadata PACKAGENAME]
[--recursive-copy-metadata PACKAGENAME] [--additional-hooks-dir HOOKSPATH] [--runtime-hook RUNTIME_HOOKS]
[--exclude-module EXCLUDES] [--splash IMAGE_FILE] [-d {all,imports,bootloader,noarchive}] [--optimize LEVEL]
[--python-option PYTHON_OPTION] [-s] [--noupx] [--upx-exclude FILE] [-c] [-w]
[--hide-console {hide-late,minimize-early,hide-early,minimize-late}]
[-i <FILE.ico or FILE.exe,ID or FILE.icns or Image or "NONE">] [--disable-windowed-traceback] [--version-file FILE]
[-m <FILE or XML>] [-r RESOURCE] [--uac-admin] [--uac-uiaccess] [--argv-emulation] [--osx-bundle-identifier BUNDLE_IDENTIFIER]
[--target-architecture ARCH] [--codesign-identity IDENTITY] [--osx-entitlements-file FILENAME] [--runtime-tmpdir PATH]
[--bootloader-ignore-signals] [--distpath DIR] [--workpath WORKPATH] [-y] [--upx-dir UPX_DIR] [--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.
options:
-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)
--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, DEPRECATION, ERROR, FATAL
(default: INFO). Also settable via and overrides the PYI_LOG_LEVEL environment variable.
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)
--contents-directory CONTENTS_DIRECTORY
For onedir builds only, specify the name of the directory in which all supporting files (i.e. everything except the
executable itself) will be placed in. Use "." to re-enable old onedir layout without contents directory.
What to bundle, where to search:
--add-data SOURCE:DEST
Additional data files or directories containing data files to be added to the application. The argument value should be
in form of "source:dest_dir", where source is the path to file (or directory) to be collected, dest_dir is the
destination directory relative to the top-level application directory, and both paths are separated by a colon (:). To
put a file in the top-level application directory, use . as a dest_dir. This option can be used multiple times.
--add-binary SOURCE:DEST
Additional binary files to be added to the executable. See the ``--add-data`` option for the format. 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. Equivalent to supplying the ``pathex`` argument in the spec file.
--hidden-import MODULENAME, --hiddenimport MODULENAME
Name an import not visible in the code of the script(s). This option can be used multiple times.
--collect-submodules MODULENAME
Collect all submodules from the specified package or module. This option can be used multiple times.
--collect-data MODULENAME, --collect-datas MODULENAME
Collect all data from the specified package or module. This option can be used multiple times.
--collect-binaries MODULENAME
Collect all binaries from the specified package or module. This option can be used multiple times.
--collect-all MODULENAME
Collect all submodules, data files, and binaries from the specified package or module. This option can be used multiple
times.
--copy-metadata PACKAGENAME
Copy metadata for the specified package. This option can be used multiple times.
--recursive-copy-metadata PACKAGENAME
Copy metadata for the specified package and all its dependencies. 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.
--splash IMAGE_FILE (EXPERIMENTAL) Add an splash screen with the image IMAGE_FILE to the application. The splash screen can display progress
updates while unpacking.
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.
--optimize LEVEL Bytecode optimization level used for collected python modules and scripts. For details, see the section “Bytecode
Optimization Level” in PyInstaller manual.
--python-option PYTHON_OPTION
Specify a command-line option to pass to the Python interpreter at runtime. Currently supports "v" (equivalent to "--
debug imports"), "u", "W <warning control>", "X <xoption>", and "hash_seed=<value>". For details, see the section
"Specifying Python Interpreter Options" in PyInstaller manual.
-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 has 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 this also triggers building a Mac OS
.app bundle. On Windows this option is automatically set if the first script is a '.pyw' file. This option is ignored on
*NIX systems.
--hide-console {hide-late,minimize-early,hide-early,minimize-late}
Windows only: in console-enabled executable, have bootloader automatically hide or minimize the console window if the
program owns the console window (i.e., was not launched from an existing console window).
-i <FILE.ico or FILE.exe,ID or FILE.icns or Image or "NONE">, --icon <FILE.ico or FILE.exe,ID or FILE.icns or Image or "NONE">
FILE.ico: apply the 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. If an image file is entered that isn't in the platform format (ico on Windows, icns on
Mac), PyInstaller tries to use Pillow to translate the icon into the correct format (if Pillow is installed). Use "NONE"
to not apply any icon, thereby making the OS show some default (default: apply PyInstaller's icon). This option can be
used multiple times.
--disable-windowed-traceback
Disable traceback dump of unhandled exception in windowed (noconsole) mode (Windows and macOS only), and instead display
a message that this feature is disabled.
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 that will request elevation upon application start.
--uac-uiaccess Using this option allows an elevated application to work with Remote Desktop.
Mac OS specific options:
--argv-emulation Enable argv emulation for macOS app bundles. If enabled, the initial open document/URL event is processed by the
bootloader and the passed file paths or URLs are appended to sys.argv.
--osx-bundle-identifier BUNDLE_IDENTIFIER
Mac OS .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)
--target-architecture ARCH, --target-arch ARCH
Target architecture (macOS only; valid values: x86_64, arm64, universal2). Enables switching between universal2 and
single-arch version of frozen application (provided python installation supports the target architecture). If not target
architecture is not specified, the current running architecture is targeted.
--codesign-identity IDENTITY
Code signing identity (macOS only). Use the provided identity to sign collected binaries and generated executable. If
signing identity is not provided, ad-hoc signing is performed instead.
--osx-entitlements-file FILENAME
Entitlements file to use when code-signing the collected binaries (macOS only).
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. Note that on POSIX systems, PyInstaller's bootloader does NOT perform shell-style
environment variable expansion on the given path string. Therefore, using environment variables (e.g., ``~`` or
``$HOME``) in path will NOT work.
--bootloader-ignore-signals
Tell the bootloader to ignore signals rather than forwarding them to the child process. Useful in situations where for
example a supervisor process signals both the bootloader and the child (e.g., via a process group) to avoid signalling
the child twice.
主要引數設定資訊：
# 指定打包輸出路徑 預設當前路徑下的dist目錄
# Where to put the bundled app (default: ./dist)
--distpath DIR
# 指定打包時的臨時檔案
# Where to put all the temporary work files, .log, .pyz and etc. (default: ./build)
--workpath WORKPATH
# 打包構建之前清除臨時檔案
# Clean PyInstaller cache and remove temporary files before building.
--clean
# 指定打包時的日誌輸出級別
# Amount of detail in build-time console messages. LEVEL may be one of TRACE, DEBUG, INFO, WARN, DEPRECATION, ERROR, FATAL
# (default: INFO). Also settable via and overrides the PYI_LOG_LEVEL environment variable.
--log-level LEVEL
# 建立包含可執行檔案的單資料夾包(預設)
# Create a one-folder bundle containing an executable (default)
-D, --onedir
# 建立一個單檔案的執行檔案。
# Create a one-file bundled executable.
-F, --onefile
# 指定打包後的檔名稱
# Name to assign to the bundled app and spec file (default: first script's basename)
-n NAME, --name NAME Name to assign to the bundled app and spec file (default: first script's basename)
# 指定檔案的icon圖示
# FILE.ico: apply the 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. If an image file is entered that isn't in the platform format (ico on Windows, icns on
# Mac), PyInstaller tries to use Pillow to translate the icon into the correct format (if Pillow is installed). Use "NONE"
# to not apply any icon, thereby making the OS show some default (default: apply PyInstaller's icon). This option can be
# used multiple times.
-i <FILE.ico or FILE.exe,ID or FILE.icns or Image or "NONE">, --icon <FILE.ico or FILE.exe,ID or FILE.icns or Image or "NONE">
# 僅視窗化（不要執行終端程序）
# Windows and Mac OS X: do not provide a console window for standard i/o. On Mac OS this also triggers building a Mac OS
# .app bundle. On Windows this option is automatically set if the first script is a '.pyw' file. This option is ignored on
# *NIX systems.
-w, --windowed, --noconsole
打包測試：
程式碼：
from PyQt6.QtWidgets import QApplication, QWidget
import sys
# Press the green button in the gutter to run the script.
if __name__ == '__main__':
app = QApplication(sys.argv)
window = QWidget()
window.setWindowTitle('PyQt6 Example')
window.setGeometry(100, 100, 800, 600)
window.show()
sys.exit(app.exec())
執行命令：pyinstaller -F -w main.py -n pyqt-example -i demo.ico
C:\Users\Administrator\PycharmProjects\pythonProject> pyinstaller -F -w main.py -n pyqt-example -i demo.ico 218 INFO: PyInstaller: 6.8.0, contrib hooks: 2024.7 218 INFO: Python: 3.11.9 226 INFO: Platform: Windows-10-10.0.22631-SP0 226 INFO: Python environment: C:\Users\Administrator\PycharmProjects\pythonProject\.venv 227 INFO: wrote C:\Users\Administrator\PycharmProjects\pythonProject\pyqt-example.spec 230 INFO: Module search paths (PYTHONPATH): ['C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Scripts\\pyinstaller.exe', 'C:\\Users\\Administrator\\AppData\\Local\\Programs\\Python\\Python311\\python311.zip', 'C:\\Users\\Administrator\\AppData\\Local\\Programs\\Python\\Python311\\DLLs', 'C:\\Users\\Administrator\\AppData\\Local\\Programs\\Python\\Python311\\Lib', 'C:\\Users\\Administrator\\AppData\\Local\\Programs\\Python\\Python311', 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv', 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages', 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject'] 389 INFO: checking Analysis 389 INFO: Building Analysis because Analysis-00.toc is non existent 389 INFO: Running Analysis Analysis-00.toc 389 INFO: Target bytecode optimization level: 0 389 INFO: Initializing module dependency graph... 390 INFO: Caching module graph hooks... 404 INFO: Analyzing base_library.zip ... 1392 INFO: Loading module hook 'hook-encodings.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 2787 INFO: Loading module hook 'hook-pickle.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 3736 INFO: Loading module hook 'hook-heapq.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 4042 INFO: Caching module dependency graph... 4131 INFO: Looking for Python shared library... 4145 INFO: Using Python shared library: C:\Users\Administrator\AppData\Local\Programs\Python\Python311\python311.dll 4145 INFO: Analyzing C:\Users\Administrator\PycharmProjects\pythonProject\main.py 4149 INFO: Loading module hook 'hook-PyQt6.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 4236 INFO: Loading module hook 'hook-PyQt6.QtWidgets.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 4368 INFO: Processing module hooks... 4414 INFO: Loading module hook 'hook-PyQt6.QtCore.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 4570 INFO: Loading module hook 'hook-PyQt6.QtGui.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 4918 INFO: Performing binary vs. data reclassification (108 entries) 4951 INFO: Looking for ctypes DLLs 4961 INFO: Analyzing run-time hooks ... 4963 INFO: Including run-time hook 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks\\rthooks\\pyi_rth_inspect.py' 4965 INFO: Including run-time hook 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks\\rthooks\\pyi_rth_pyqt6.py' 4968 INFO: Processing pre-find module path hook _pyi_rth_utils from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks\\pre_find_module_path\\hook-_pyi_rth_utils.py'. 4969 INFO: Loading module hook 'hook-_pyi_rth_utils.py' from 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks'... 4972 INFO: Including run-time hook 'C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyInstaller\\hooks\\rthooks\\pyi_rth_pkgutil.py' 4979 INFO: Looking for dynamic libraries 5085 INFO: Extra DLL search directories (AddDllDirectory): ['C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyQt6\\Qt6\\bin'] 5085 INFO: Extra DLL search directories (PATH): ['C:\\Users\\Administrator\\PycharmProjects\\pythonProject\\.venv\\Lib\\site-packages\\PyQt6\\Qt6\\bin'] 5979 INFO: Warnings written to C:\Users\Administrator\PycharmProjects\pythonProject\build\pyqt-example\warn-pyqt-example.txt 5997 INFO: Graph cross-reference written to C:\Users\Administrator\PycharmProjects\pythonProject\build\pyqt-example\xref-pyqt-example.html 6020 INFO: checking PYZ 6020 INFO: Building PYZ because PYZ-00.toc is non existent 6020 INFO: Building PYZ (ZlibArchive) C:\Users\Administrator\PycharmProjects\pythonProject\build\pyqt-example\PYZ-00.pyz 6258 INFO: Building PYZ (ZlibArchive) C:\Users\Administrator\PycharmProjects\pythonProject\build\pyqt-example\PYZ-00.pyz completed successfully. 6283 INFO: checking PKG 6283 INFO: Building PKG because PKG-00.toc is non existent 6283 INFO: Building PKG (CArchive) pyqt-example.pkg 14096 INFO: Building PKG (CArchive) pyqt-example.pkg completed successfully. 14100 INFO: Bootloader C:\Users\Administrator\PycharmProjects\pythonProject\.venv\Lib\site-packages\PyInstaller\bootloader\Windows-64bit-intel\runw.exe 14100 INFO: checking EXE 14100 INFO: Building EXE because EXE-00.toc is non existent 14100 INFO: Building EXE from EXE-00.toc 14100 INFO: Copying bootloader EXE to C:\Users\Administrator\PycharmProjects\pythonProject\dist\pyqt-example.exe 14111 INFO: Copying icon to EXE 14302 INFO: Copying 0 resources to EXE 14302 INFO: Embedding manifest in EXE 14482 INFO: Appending PKG archive to EXE 14513 INFO: Fixing EXE headers 14694 INFO: Building EXE from EXE-00.toc completed successfully. (.venv) PS C:\Users\Administrator\PycharmProjects\pythonProject>
