Update pyinstaller to 6.20.0 by pyup-bot · Pull Request #235 · scieloorg/scielobooks_exports

pyup-bot · 2026-04-22T21:33:50Z

This PR updates PyInstaller from 5.9.0 to 6.20.0.

Changelog

6.20.0

-------------------

Bugfix
~~~~~~

* (Linux) Fix binary dependency analysis in Termux environment; previously,
no binary dependencies would be reported due to mismatched ``ldd`` output
pattern. (:issue:`9402`)
* (Linux) Fix compatibility issues with Termux python 3.13, caused by
platform being now reported as &quot;android&quot; instead of &quot;linux&quot; (PEP 738).
(:issue:`9398`)
* (macOS) Fix built-time error when trying to create an .app bundle with
data collected from a directory that contains symlinked elements.
(:issue:`9375`)
* Fix the ``forkserver`` spawn mode of ``multiprocessing`` under python
3.13.13, 3.14.4, and the upcoming 3.15. (:issue:`9423`)
* Remove warning about non-existing ``tclX`` module directory; in some Tcl
distributions (e.g., Debian-packaged Tcl), this directory is located
under the main library/data directory, and therefore the stand-alone
directory neither exists nor needs to be explicitly collected.
(:issue:`9401`)


Hooks
~~~~~

* Prevent the run-time hook for ``gi.repository.GLib`` from overriding
the implicit default value of the ``XDG_DATA_DIRS`` environment
variable (i.e., ``/usr/local/share/:/usr/share/``) when adding the
frozen application&#x27;s top-level directory to the list of data directories.
(:issue:`9422`)
* Update ``gi.repository.Gio`` hook to collect corresponding platform-specific
typelib (``GioWin32`` or ``GioUnix``), and add hooks for these modules.
This aims to prevent potential run-time errors, either because the typelib
is missing, or because it was opportunistically loaded from the run-time
system and happens to be of incompatible version. (:issue:`9410`)
* Update ``gi.repository.GLib`` hook to collect corresponding platform-specific
typelib (``GLibWin32`` or ``GLibUnix``), and add hooks for these modules.
This aims to prevent potential run-time errors, either because the typelib
is missing, or because it was opportunistically loaded from the run-time
system and happens to be of incompatible version. (:issue:`9410`)


Bootloader
~~~~~~~~~~

* (Windows) Add new option to the ``waf`` build script, ``--no-cfg``,
that allows bootloader to be built without Control Flow Guard (CFG)
enabled. Applicable only when building with MSVC toolchain. (:issue:`9352`)
* Fix errors when compiling with ``glibc`` 2.43 and compiler that defaults
to using C23 standard. (:issue:`9371`)
* Rework the handling of unknown target CPU architectures in the bootloader
build script, and add identification for ``loongsoon`` and ``sunway`` to
the bundled copy of ``waflib``. The bootloader directories for these
platforms now use PyInstaller&#x27;s normalized platform name (i.e.,
``Linux-64bit-loongarch`` and ``Linux-64bit-sunway`` instead of
former ``Linux-64bit-loongarch64`` and ``Linux-64bit-sw_64``). (:issue:`9403`)
* Update the bundled zlib sources to v1.3.2. (:issue:`9384`)

6.19.0

-------------------

Bugfix
~~~~~~

* (Windows) Fix collection of ``numpy`` DLLs when ``numpy`` PyPI wheel is
installed using ``uv`` instead of ``pip``. (:issue:`9360`)
* Extend suppression of missing ``api-ms-win-*.dll`` warnings to Windows Server
(formerly Windows 10 and 11). (:issue:`9355`)
* (Conda) Fix error during initialization of the `conda` hook utility module in
Anaconda environments where the metadata for packages with no dependencies
omit their *dependencies* key. (:issue:`9345`)


Hooks
~~~~~

* (Windows) Fix installer check in ``numpy`` hook to enable explicit collection
of DLLs from ``numpy.libs`` directory when ``numpy`` PyPI wheels are installed
through an installer other than ``pip`` - for example, ``uv``. (:issue:`9365`)
* (Windows) Update the ``pandas`` hook to explicitly collect the DLLs
from ``pandas.libs`` directory that has been used in Windows PyPI wheels
since ``pandas`` 2.1.0. (:issue:`9365`)

6.18.0

-------------------

Features
~~~~~~~~

* Implement support for Tcl/Tk 9 in splash screen. (:issue:`9313`)


Bugfix
~~~~~~

* (macOS) Improve the .framework bundle fix-up code to remove file entries
that would be placed under restored symlinked directories. This fixes
file-already-exists errors at build time (onedir) or run-time (onefile)
when user or a hook tries to collect (all) files from a package that
ships a .framework bundle with symlinks mangled into hard-copies
(for example, due to lack of symlink support in PyPI wheels). (:issue:`9335`)
* Have hook for stdlib ``platform`` module exclude the ``_ios_support``
module when ``sys.platform != &#x27;ios&#x27;``. This prevents unnecessary
collection of ``ctypes``-imported ``libobjc`` shared library if the
latter happens to be available on the build system. (:issue:`9333`)


Hooks
~~~~~

* Update ``scipy`` hook for compatibility with ``scipy`` 1.17.0.
(:issue:`9353`)


Bootloader
~~~~~~~~~~

* (Windows) When spawning ``onefile`` child process, preserve the values of
``dwFlags`` and ``wShowWindow`` in ``STARTUPINFO`` structure as inherited
from the parent process, instead of forcing them to ``STARTF_USESHOWWINDOW``
and ``SW_NORMAL``. (:issue:`9342`)

6.17.0

-------------------

Bugfix
~~~~~~

* Avoid indirect usage of ``pkg_resources`` which is deprecated and scheduled to
be removed in 2025-11-30. (:issue:`9149`)
* Revise the search for Python shared library from :issue:`9218` and
the restrictions it imposes: enable the fall-back codepath with
guess-based name for all Python builds that report ``Py_ENABLE_SHARED=0``
instead of just for Anaconda Python (``compat.is_conda``), but limit
the search paths in this fall-back codepath to only ``sys.base_prefix``
and the ``lib`` directory under it. (:issue:`9276`)
* Work around performance issues introduced by superfluous usage of
:func:`gc.collect` in ``pefile==2024.8.26``. PyInstaller no longer blocks
:installing ``pefile==2024.8.26``. (:issue:`8762`)


Hooks
~~~~~

* Fix finding setuptools&#x27;s vendored copies of ``backports`` and ``jaraco``
packages. (:issue:`9250`)

6.16.0

-------------------

Features
~~~~~~~~

* (POSIX) Adjust the destination directory for collected python&#x27;s standard
extensions, from ``lib-dynload`` to ``python3.x/lib-dynload`` directory,
in order to preserve the relative relationship between the extension
location and the (grand-parent) shared library directory that is commonly
found in POSIX python environments. This is required for compatibility
with upcoming Linux builds of ``astral-sh/python-build-standalone`` that
will set relative library paths in extensions via both ``DT_NEEDED`` and
``DT_RPATH``. (:issue:`9212`)
* Rework the anonymization of the ``co_filename`` attribute in collected
code objects - instead of trying to obtain anonymized relative name by
removing known path prefixes from the original absolute-path ``co_filename``,
we now construct the anonymized relative name directly from the collected
module&#x27;s (or script&#x27;s) destination name w.r.t. its destination container
(i.e., the ``PKG`` archive, the ``PYZ`` archive, or the ``base_library.zip``
archive). (:issue:`9226`)
* Rework the search for python shared library in order to reduce amount of
guess-work and better accommodate variations in naming across platforms
and due to different build options (e.g., debug build with &quot;d&quot; suffix,
free-thread build with &quot;t&quot; suffix, combination of both).

On Windows, the loaded python DLL is now resolved by calling
``GetModuleFileName``
on the handle exposed by :data:`sys.dllhandle`; this applies to python.org
Windows
builds, Anaconda python on Windows, and MSYS2 python.

On other platforms, first explicitly verify that shared library is enabled,
by checking the value of ``Py_ENABLE_SHARED`` variable exposed by the
``sysconfig`` module. On macOS, also check if .framework bundle is
enabled instead, which is implied by a non-empty ``PYTHONFRAMEWORK``
variable in ``sysconfig``. If shared library is enabled, use ``INSTSONAME``
variable exposed by ``sysconfig`` module as the only source of truth
w.r.t. its name. This works even with Debian-packaged python and
``astral-sh/python-build-standalone`` POSIX builds; while they have
their ``python`` executable statically linked against python shared
library, they seem to properly set these variables.

In contrast, both Linux and macOS builds of Anaconda python seem to
build their interpreter executable and python shared library separately,
so the interpreter reports ``Py_ENABLE_SHARED`` variable to be set to ``0``
(and ``INSTSONAME`` gives name of the static library). Therefore, for
Anaconda python on non-Windows, use the old approach of guessing the
library name from the major and minor version and whether free-threading
is enabled or not (i.e., the presence of the &quot;t&quot; suffix).

Adjust the error messages; display the part about rebuilding python with
``--enable-shared`` option only if we detect lack of support for shared
library. Similarly, display the part about Debian package only if we
are running under Debian or its derivative; and advise to install
``libpython3.X`` package rather than ``python3-dev``. (:issue:`9218`)


Hooks
~~~~~

* Add hook for ``gi.repository.OsmGpsMap``. (:issue:`9209`)

6.15.0

-------------------

Features
~~~~~~~~

* Add Python 3.14 support. (:issue:`9192`)


Bugfix
~~~~~~

* (non-Windows) Ensure that binary dependency analysis creates symbolic
links in top-level application directory for shared libraries that are
not resolvable during binary dependency analysis but are nevertheless
collected due to being explicitly collected by a hook or by the user.
(:issue:`9186`)
* Attempt to mitigate the issue with module exclusion when a top-level
package hook excludes its own subpackage to prevent its collection
in the absence of any external references; such exclusion rule would
prevent collection of modules from such subpackage even when it is
supposed to be collected due to an external reference (for example, an
explicit import from the user&#x27;s program). (:issue:`9193`)
* Fix a bug in module exclusion part of analysis codepath that would cause
certain types of relative imports to be misinterpreted and thus fail to
exclude them. (:issue:`9197`)

6.14.2

-------------------

Bugfix
~~~~~~
 
* Exclude ``libsocket.so`` on Solaris as this is specific to the Solaris
installation and causes symbol errors otherwise. (:issue:`9171`)


Hooks
~~~~~

* Update ``scipy`` hooks for compatibility with ``scipy`` 1.6.0.
(:issue:`9180`)


Bootloader build
~~~~~~~~~~~~~~~~

* Fix compiling bootloader on Solaris 10 systems. (:issue:`9171`)

6.14.1

-------------------

Hooks
~~~~~

* Update the ``numpy`` hook for compatibility with NumPy v2.3.0.
(:issue:`9162`)

6.14.0

-------------------

Bugfix
~~~~~~

* (AIX) Fix the name of Tcl and Tk shared libraries used by splash screen;
if said shared libraries are ``.a`` archives, we need to load the shared
object from the archives (e.g., ``libtcl.a(libtcl.so.8.6)`` and
``libtk.a(libtk.so.8.6)``). (:issue:`9111`)
* (AIX) Fix use of ``strip`` utility on collected binaries; pass the
``-x32_64``
flag to enable transparent processing of either 32-bit or 64-bit binaries.
Suppress warnings on ``strip`` errors when a collected binary is already
stripped. (:issue:`9111`)
* (Windows) Fix collection of DLLs from Anaconda-installed ``numpy`` and
its dependencies (MKL, OpenBLAS, TBB, etc.) when the file paths recorded
in the metadata end up using Windows-style separators instead of POSIX
ones. (:issue:`9113`)
* Fix behavior of :option:`--add-data` and :option:`--add-binary` when the
given source path contains a glob that matches directories. PyInstaller
now collects the matched directories themselves into the specified target
directory instead of collecting their content into the specified target
directory (i.e., the directories are preserved). This ensures that
``--add-data data_dir:data_dir`` and ``--add-data data_dir/*:data_dir``
end up behaving in the same way when the data directory contains
sub-directories. (:issue:`9108`)
* The ``Analysis()`` class now keeps track of pure-python modules that are not
collected into PYZ archive (i.e., are not listed in the ``Analysis.pure``
TOC list); the corresponding entries are added to a separate TOC list
that is also under modification-time check, which allows us to detect
modifications and re-run the analysis. (:issue:`9135`)
* When collecting files for splash screen, suppress warning about
``license.terms`` not being found in the ``tk8.x`` directory; this seems
to be the case in most Tcl/Tk installations found on POSIX systems.
(:issue:`9111`)


Hooks
~~~~~

* Add pre-safe-import-module hook for ``gi.overrides`` to properly handle
cases where the ``gi.overrides`` package is split between
``/usr/lib64/python3.X/site-packages/gi/overrides`` and
``/usr/lib/python3.X/site-packages/gi/overrides`` (i.e., RPM packages
for Fedora/RHEL and their derivatives, such as openEuler). (:issue:`9126`)
* Have the ``pytz`` hook exclude ``pkg_resources``, to prevent the latter
from being collected due to a reference in the fallback resource
loading codepath in ``pytz`` that should normally not be reached.
(:issue:`9154`)
* Remove the hook for ``packaging``; the only function of this hook was
to add ``pkg_resources`` to hidden imports, which nowadays results in
``pkg_resources`` (and our run-time hook for it) being unnecessarily
collected into frozen application and, with up-to-date ``setuptools``
triggers a deprecation warning at run-time. (:issue:`9151`)


Bootloader
~~~~~~~~~~

* (Linux) The bootloader now preserves its original process name (for example,
when executable is symlinked with different basename) when the ``onedir``
process restarts itself for the library-search-path changes to take affect.
The original process name is now also propagated to sub-processes that are
spawned using the same executable (for example, using Python&#x27;s
:mod:`subprocess` module and :data:`sys.executable`). (:issue:`9118`)
* (POSIX) On POSIX systems where library search path is set by modifying
``LD_LIBRARY_PATH`` environment variable (or equivalent), the parent
process of ``onefile`` application with enabled splash screen now
restarts itself, in order to apply library search path modification
before splash screen is started and Tcl/Tk shared libraries are loaded.
This ensures that bundled dependencies of Tcl/Tk shared libraries can
be discovered and loaded, instead of having to rely on system copies
being available. (:issue:`9118`)


Module Loader
~~~~~~~~~~~~~

* Have the ``PyiFrozenLoader`` use the .py suffix instead of .pyc one
for module&#x27;s file path (the file path stored in the loader&#x27;s ``path``
attribute and the module&#x27;s ``__file__`` attribute). This should improve
compatibility with 3rd party code that assumes that the module&#x27;s
``__file__`` attribute points to the source .py file; odd-case scenarios
such as checking for file&#x27;s existence, trying to query its creation time
or trying to read it as a source file can now be accommodated by simply
collecting the source .py files, rather than also having to exclude the
byte-compiled module from the PYZ archive. (:issue:`9141`)


Documentation
~~~~~~~~~~~~~

* Update documentation about building bootloader on AIX; add a note about
``/opt/freeware/gcc`` from *AIX Toolbox for Open Source Software* not
honoring the :envvar:`OBJECT_MODE` environment variable. (:issue:`9111`)


Bootloader build
~~~~~~~~~~~~~~~~

* (AIX) Pass ``-X32_64`` flag to ``strip`` utility to have it transparently
process either 32-bit or 64-bit executable, without user having to explicitly
set the :envvar:`OBJECT_MODE` environment variable. (:issue:`9111`)
* Prevent the ``strip`` utility from being ran twice when building bootloader
executables; fixes errors with ``strip`` utilities that disallow being
ran against already-stripped binaries (for example, the ``strip`` utility
on AIX). (:issue:`9111`)
* Remove duplicated check for the ``strip`` utility. (:issue:`9111`)
* When building bootloader with a cross-compiler toolchain, have the build
script look for toolchain-provided version of ``strip`` utility (for
example, ``powerpc64le-linux-gnu-strip`` that is shipped with
``powerpc64le-linux-gnu-gcc``) and prefer it over the system-provided one.
(:issue:`9111`)

6.13.0

-------------------

Features
~~~~~~~~

* (macOS) When assembling the executable, PyInstaller now modifies the
Mach-O image UUID of all architecture slices in the executable, and
sets them to a value derived from the hash of the embedded PKG archive
and the original (bootloader&#x27;s) UUID. This should ensure that different
application executables have unique identifiers, as per
`TN3178
&lt;https://developer.apple.com/documentation/technotes/tn3178-checking-for-and-resolving-build-uuid-problems&gt;`_,
which might be required by newer macOS features, such as
`local network privacy
&lt;https://developer.apple.com/documentation/technotes/tn3179-understanding-local-network-privacy#Build-time-considerations&gt;`_.
(:issue:`9056`)
* Extend analysis code so that when extension module is encountered, it
checks for the presence of an adjacent ``.py`` or ``.pyi`` file, and
if present, attempt to perform import analysis on such accompanying
source/interface file. (:issue:`9084`)


Bugfix
~~~~~~

* (Windows) Fix (de)serialization of ``WORD``-typed fields in the
``VersionInfo`` structure - it should be using 16-bit unsigned integer
format (``&#x27;H&#x27;``) instead of signed one (``&#x27;h&#x27;``). This, for example,
fixes the ``struct.error: &#x27;h&#x27; format requires -32768 &lt;= number &lt;= 32767``
error when ``VersionInfo`` contains a ``VarFileInfo`` / ``VarStruct``
entry with the code page set to 65001. (:issue:`9086`)
* Fix detection of ``setuptools``-vendored modules (i.e., not packages)
in the ``PyInstaller.utils.hooks.setuptools.SetuptoolsInfo`` hook utility
class; for example, the ``setuptools/_vendor/typing_extensions.py`` module.
(:issue:`9102`)


Deprecations
~~~~~~~~~~~~

* Onefile in combination with macOS&#x27;s .app bundles will be blocked in v7.0.
Onefile app bundles are not really single file and are heavily penalised by
macOS&#x27;s security scanning. Please use onedir mode instead. (:issue:`9049`)


Hooks
~~~~~

* Add hook for ``PyQt6.QtStateMachine`` that was introduced in ``PyQt6``
v6.8.1. (:issue:`9019`)
* Fix ``ModuleNotFoundError`` for ``scipy`` when provided by Debian&#x27;s
``python3-scipy`` package. (:issue:`9069`)
* Update hook for ``PyGObject`` (``gi``) and associated helper code to
support changes made in ``PyGObject`` v3.52 (switch from ``girepository-1.0``
to ``girepository-2.0``). (:issue:`9055`)


Bootloader
~~~~~~~~~~

* (Windows) Have the parent process of ``onefile`` application always
attempt to pre-load system copies of VC runtime DLLs, i.e.,
``VCRUNTIME140.dll`` and ``VCRUNTIME140_1.dll``. This extends the
pre-load work-around from :issue:`8650` that aims to resolve issues
with bundled VC runtime DLLs not being cleaned up from the application&#x27;s
temporary directory when 3rd party DLLs are injected into the process
(by the OS, an anti-virus program, or some 3rd party component).
(:issue:`9075`)
* On POSIX systems other than macOS, use POSIX semaphore API instead of
SysV semaphore API to synchronize ``onefile`` parent and child process.
This restores the ability to compile bootloader under Termux, where
``sys/sem.h`` (and the SysV semaphore API) is unavailable due to deliberate
lack of support for it in the underlying Android base. (:issue:`9089`)

6.12.0

-------------------

Features
~~~~~~~~

* (Cygwin) Improve Cygwin support to the extent that we can run a
Cygwin-based CI pipeline with basic part of PyInstaller&#x27;s test suite.
(:issue:`8972`)
* Extend the :ref:`module_collection_mode &lt;package collection mode&gt;` setting
from :issue:`6945` to also apply to modules collected into
``base_library.zip`` archive. Implement discovery of source .py files for
modules in ``base_library.zip`` at run-time. This allows collection and
discovery of source .py files for modules in ``base_library.zip``, which might
be required by frameworks that perform aggressive recursive introspection all
way down to standard library modules (for example, ``torch`` JIT in
combination with certain model implementations). (:issue:`8971`)


Bugfix
~~~~~~

* (AIX) Fix spurious run-time error in bootloader when no Wflags and/or no
Xflags are specified via bootloader&#x27;s run-time options (i.e., most of the
time). (:issue:`9006`)
* (macOS) Fix directory name sanitization when building macOS .app bundles
to properly account for nested .framework bundles, and prevent mangling
of .framework directory name of all but inner-most .framework bundles.
For example, the ``sdl2dll/dll/SDL2_image.framework`` directory from
``pysdl2-dll`` PyPI wheels would become mangled into
``sdl2dll/dll/SDL2_image__dot__framework`` due to having nested
.framework bundles in its ``Versions/A/Frameworks`` sub-directory.
(:issue:`8936`)
* (macOS) Have binary dependency analysis obtain the actual lists of
run paths set on the python executable (:data:`sys.executable`), instead of
assuming that it is effectively set to ``loader_path/../lib``. This
enables discovery of shared libraries bundled with python builds that
use different origin for their run paths and ``rpath``-based references.
(:issue:`8951`)
* (macOS) Prevent binary dependency analysis from spuriously resolving
shared library instance in a standard library path (for example,
Homebrew-installed library in ``/usr/local/lib``) when trying to
resolve ``rpath``-based reference with multiple candidate run paths
that are anchored to ``loader_path`` or ``executable_path`` prefix
that resolves to a completely different path prefix (for example, an
Anaconda python environment). (:issue:`8962`)
* Add exclude for ``libwayland*.so`` to prevent mismatches with system drivers.
(:issue:`8963`)
* Fix errors raised by ``setuptools`` hook utility class and various
related hooks when building with completely de-vendored ``setuptools``
(for example, as packaged by Arch Linux). (:issue:`8947`)
* Gracefully handle cases when ``_tkinter`` is a built-in instead of an
extension module, and thus does not have a ``__file__`` attribute.
Most notable example of this are `indygreg&#x27;s python-build-standalone
CPython builds &lt;https://github.com/astral-sh/python-build-standalone&gt;`_
for macOS and Linux. This fixes collection of ``tkinter`` and associated
Tcl/Tk resources when using such python builds. When trying to enable
splash screen, a descriptive error is now raised, because splash screen
requires shared Tcl/Tk libraries, while a built-in ``_tkinter`` seems to
indicate that python was statically linked against Tcl/Tk libraries.
(:issue:`9012`)
* Rework the ``localpycs`` cache in the ``build`` directory to avoid relying
on the source .py file timestamps. Some package managers (e.g., Anaconda)
(re)set the file creation/modification time of installed files to the
time of packaging rather than having them reflect the time of installation;
therefore, the PyInstaller bootstrap script and modules would fail to be
properly recompiled when switching between different versions of
PyInstaller packaged by Anaconda. (:issue:`8909`)
* When constructing ``PyiFrozenFinder`` for the given path and trying
to compute the path that is relative to the top-level application
directory, do not fully resolve the given path. Instead, try computing
relative path using both the original and the fully resolved top-level
application directory path. This change prevents us from potentially
resolving symbolic links in parts of the given path that do not belong
to the top-level application directory. (:issue:`8994`)


Incompatible Changes
~~~~~~~~~~~~~~~~~~~~

* (Cygwin) PyInstaller does not attempt to collect ``cygwin1.dll`` anymore.
If you want to create &quot;stand-alone&quot; Cygwin-based frozen application, you
need to place a copy of the DLL next to the frozen application&#x27;s
executable, and distribute them together. See :ref:`Cygwin-specific section
of Platform-specific Notes &lt;Platform-specific Notes - Cygwin&gt;` for details.
(:issue:`8972`)


Hooks
~~~~~

* Add hook for ``gi.repository.Rsvg``. (:issue:`8940`)
* Add hooks for ``PyQt6.QtGraphs`` and ``PyQt6.QtGraphsWidgets`` that
were introduced in ``PyQt6`` v6.8.1 (via ``PyQt6-Graphs`` add-on package).
(:issue:`8924`)


Module Loader
~~~~~~~~~~~~~

* Split the ``PyiFrozenImporter`` (fused `path based finder
&lt;https://docs.python.org/3/glossary.html#term-path-based-finder&gt;`_
and `loader &lt;https://docs.python.org/3/glossary.html#term-loader&gt;`_)
into separate finder (``PyiFrozenFinder``) and loader (``PyiFrozenLoader``).
This better matches the separation between python&#x27;s built-in finders and
loaders, and thus accommodates 3rd-party code that naively expects to
encounter only python&#x27;s built-in finders and loaders. (:issue:`8934`)


Documentation
~~~~~~~~~~~~~

* Add notes about Cygwin and ``cygwin1.dll`` under new :ref:`Cygwin-specific
section of Platform-specific Notes &lt;Platform-specific Notes - Cygwin&gt;`.
(:issue:`8972`)


Bootloader build
~~~~~~~~~~~~~~~~

* The stock Linux bootloaders are now built using generic Ubuntu 18.04 and
Alpine
3.12 Docker images rather than manylinux/musllinux/dockcross. (:issue:`8881`)

6.11.1

-------------------

Bugfix
~~~~~~

* (GNU/Linux) Fix resolving binary dependencies linked using ``$ORIGIN``.
(:issue:`8868`)
* (Linux) Fix discovery and collection of Python shared library when using
``uv``-installed or ``rye``-installed Python that happens to be of same
version as the system-installed Python. (:issue:`8850`)
* (Linux/musl) Prevent ``ld-musl-x86_64.so.1`` from being collected.
(:issue:`8868`)
* (Windows) Add a retry loop to ``onefile`` temporary directory cleanup
as an attempt to mitigate situations when bundled DLLs and python
extension modules remain locked by the OS and/or anti-virus program
for a short while after the application process exits. (:issue:`8870`)
* (Windows) Fix Qt run-time hooks failing to add the top-level application
directory to ``PATH`` when the latter already contains a sub-directory
of the top-level application directory (for example, ``pywin32_system32``
sub-directory added to ``PATH`` by ``pywin32`` run-time hook). This
failure prevented QtNetwork from discovering bundled OpenSSL DLLs, and
caused it to (attempt to) load them from other locations that happened
to be in ``PATH``. (:issue:`8857`)
* Fix macOS&#x27;s default icons being missing from wheels (regression introduced in
v6.11.0) (:issue:`8855`)
* Prevent :mod:`tkinter` from being collected if it is unusable.
(:issue:`8868`)


Hooks
~~~~~

* Prevent ``IPython`` from being packaged redundantly if ``matplotlib`` is
imported. (:issue:`8868`)

6.11.0

-------------------

Features
~~~~~~~~

* Implement a mechanism that allows hooks to inform PyInstaller&#x27;s binary
dependency analysis that it should not create symbolic links to top-level
application directory for certain shared libraries (applicable to platforms
where such symbolic links are created in the first place). This mechanism
is intended as a work around for corner cases when such symbolic links
disrupt run-time discovery of other shared libraries that are stored in
the linked library&#x27;s true location. (:issue:`8761`)


Bugfix
~~~~~~

* (Windows) Allow PyInstaller to be launched from SYSTEM user&#x27;s home
directory (``%WINDIR%\system32\config\systemprofile``) and its
sub-directories, as an exception to general prohibition of running
from Windows directory and its sub-directories (which was introduced
in :issue:`8570`). (:issue:`8816`)
* (Windows) Attempt to mitigate timing issues that prevented console
hiding/minimization mechanism (:issue:`7735`) from taking effect when
Windows Terminal is used as the default terminal app. (:issue:`8798`)
* (Windows) Fix binary dependency analysis for files found under
SYSTEM user&#x27;s home directory (``%WINDIR%\system32\config\systemprofile``)
when running PyInstaller as SYSTEM user. (:issue:`8810`)
* (Windows) Fix regression with PyInstaller 6.x and ``numpy`` &lt; 1.26
that resulted in duplicated shared libraries bundled with ``numpy``
PyPI wheels. (:issue:`8736`)
* (Windows) Fix the leak of ``VCRUNTIME140.dll`` in ``onefile`` applications
with splash screen enabled, this time in scenarios with full application
restart (regression introduced by :issue:`8650`). (:issue:`8701`)
* Fix a regression when trying to use ``runpy.run_path`` to run a python
script bundled with the frozen application. (:issue:`8767`)


Hooks
~~~~~

* Add hook for ``PySide6.QtGraphsWidgets``, which was introduced with
``PySide6`` v6.8.0. (:issue:`8828`)
* Tweak the ``setuptools`` hook to minimize collection of vendored
packages/modules and their (meta)data when using ``setuptools`` &gt;= 71.0;
the aim is to have the run-time behavior of collected vendored package
closely match the behavior of its non-vendored counterpart. (:issue:`8737`)
* Update ``babel`` hook to collect all submodules that are needed to
unpickle the bundled locale data files. (:issue:`8750`)
* Update and modernize PyInstaller&#x27;s copy of ``numpy`` hook for compatibility
with ``numpy`` 1.24.x, 1.25.x, 1.26x, and 2.x. Set the priority of
PyInstaller&#x27;s copy of ``numpy`` hook to 1 (using the new hook priority
mechanism from :issue:`8740`), so that it overrides the upstream hook, in
attempt to address the following issues:

- fix duplication of shared libraries bundled with ``numpy`` &lt; 1.26
 PyPI wheels on Windows, which is caused by changed behavior of
 PyInstaller&#x27;s binary dependency analysis in PyInstaller 6.x (both the
 old version of PyInstaller&#x27;s numpy hook and its upstream counterpart
 were written for behavior of v5 and earlier).

- avoid triggering a warning about ``numpy`` base dist not being
 found when using ``pip``-installed ``numpy`` with Anaconda python.

- with ``numpy`` &gt;= 1.26 on Windows, collect the load-order file from
 ``numpy.libs`` directory (if available) along with the shared libraries.
 This should minimize potential issues when using ``pip``-installed
 ``numpy`` &gt;= 1.26 with Anaconda python 3.8 and 3.9. (:issue:`8799`)


Bootloader
~~~~~~~~~~

* (AIX) Fix errors when compiling bootloader under AIX (regression
introduced in PyInstaller v6.8). (:issue:`8819`)
* (Cygwin) Fix missing-variable-error when compiling bootloader under
Cygwin (regression introduced in PyInstaller v6.8). (:issue:`8814`)


Documentation
~~~~~~~~~~~~~

* Document the caveats of enabling the hiding/minimization mechanism in
the frozen application when Windows Terminal is configured as the default
terminal app on the run-time system. (:issue:`8798`)


PyInstaller Core
~~~~~~~~~~~~~~~~

* (Windows) Pin ``pefile != 2024.8.26`` due to performance regression in
``pefile`` 2024.8.26 that heavily impacts PyInstaller&#x27;s binary dependency
analysis and binary-vs-data classification. (:issue:`8762`)


Bootloader build
~~~~~~~~~~~~~~~~

* Relax the check for ``libdl`` to accommodate platforms which put the
``libdl``
symbols in ``libc`` but don&#x27;t provide the placeholders needed to adhere to
the
POSIX requirement that ``-ldl`` should always be available, most notably
OpenWRT. (:issue:`7552`)

6.10.0

-------------------

Features
~~~~~~~~

* (Linux) Extend the mechanism for collection of ``.hmac`` files from
:issue:`8288` to also include ``.hmac`` files in the ``fipscheck`` directory.
(:issue:`8719`)
* Add support for Python 3.13. (:issue:`8198`)

* Introduce new :envvar:`PYINSTALLER_RESET_ENVIRONMENT` environment variable, to
be used by application developers when trying to launch
:data:`sys.executable`-based process that is supposed to outlive the current
application process (which includes the :ref:`application restart scenario
&lt;independent subprocess&gt;`). This is considered the official and preferred
approach at spawning new independent instances of the same application (as
opposed to modifying the private :envvar:`_PYI_ARCHIVE_FILE` environment
variable). (:issue:`8634`)
* The splash screen in splash-screen enabled frozen application can now
be disabled by the user at run-time, using the new
:envvar:`PYINSTALLER_SUPPRESS_SPLASH_SCREEN` environment variable. If the
environment variable is set to ``1``, the splash screen is not shown,
and functions from :mod:`pyi_splash` become no-op without raising errors
or displaying warning messages. (:issue:`8634`)


Bugfix
~~~~~~

* (Windows) Attempt to work around the leak of ``VCRUNTIME140.dll`` in
``onefile`` applications with splash screen enabled in scenarios where
the OS and/or anti-virus program injects additional DLLs into the process
that also depend on ``VCRUNTIME140.dll``. (:issue:`7106`)
* (Windows) Fix regression in PyInstaller 6.x that caused console-enabled
onefile to applications fail to clean up their temporary directory during
system session shutdown (i.e., when user logs off or initiates system shutdown
or restart). For console-enabled onefile applications, this used to work up
until PyInstaller 6.0 by means of installed console handler; however, due to
contemporary bootloader executables being linked against ``user32.dll``, the
console handler does not receive ``CTRL_LOGOFF_EVENT`` and
``CTRL_SHUTDOWN_EVENT`` console events anymore (for the same reason, this did
not work for builds with splash screen, even between v5.3 and 6.0). Instead,
session shutdown is now handled by means of hidden window and handling of
``WM_QUERYENDSESSION`` and ``WM_ENDSESSION`` event messages. (:issue:`8648`)
* (Windows) Improve handling of ``CTRL_CLOSE_EVENT`` console event in
``onefile`` builds for compatibility with Windows Terminal in order to
avoid leaking temporary files when user closes the terminal window
(or tab). Upon receiving the event, the parent process now gives the child
process a 500-millisecond grace period to exit, after which it terminates
the child process and proceeds with the cleanup (previously, the parent
process indefinitely waited for the child to exit, under assumption that
the ``CTRL_CLOSE_EVENT`` will also cause the child to exit at the same
time – which was the case with ``conhost.exe``, but is not the case with
Windows Terminal, where the child appears to receive event only after
OS already terminated the parent process). (:issue:`8640`)
* (Windows) The windowed/noconsole ``onefile`` builds should now clean up
their temporary directories during session shutdown (i.e., when user logs
off or initiates system shutdown or restart). (:issue:`8648`)
* Fix the implementation of ``PyiFrozenResourceReader.files()`` when called
with (sub)module name, it should return the path to the module&#x27;s parent
(package) directory, instead of a sub-directory with module&#x27;s name.
(:issue:`8659`)
* The ``MERGE`` dependency processing code now uses both source and destination
path as a bookkeeping key (instead of just source path). This fixes issues
when using ``MERGE`` with application TOCs that contain entries for a file
that is collected more than once, with different destination names.
(:issue:`8687`)
* The splash screen is now automatically suppressed in worker sub-processes
spawned via :data:`sys.executable`. The splash screen is not shown, and
functions from :mod:`pyi_splash` become no-op without raising errors or
displaying warning messages. (:issue:`8634`)


Incompatible Changes
~~~~~~~~~~~~~~~~~~~~

* Attempting to restart the application by spawning new process via
:data:`sys.executable` and exiting the current process now requires the
:envvar:`PYINSTALLER_RESET_ENVIRONMENT` environment variable to be set prior
to spawning the process. See :ref:`independent subprocess`. (:issue:`8634`)


Deprecations
~~~~~~~~~~~~

* The ``-m`` shorthand for :option:`--manifest` will be removed in v7.0.
(:issue:`2560`)


Hooks
~~~~~

* Clean up the ``multiprocessing`` run-time hook. Due to changes in detection
of inherited PyInstaller environments, we do not need to restore (the now
renamed) ``_MEIPASS2``  environment variable anymore, and we can remove
all our custom ``Popen`` overrides. (:issue:`8634`)
* Implement support for ``setuptools`` &gt;= 71.0.0 and its new approach to
vendoring its dependencies. (:issue:`8720`)


Bootloader
~~~~~~~~~~

* (Linux) When frozen executable is launched via dynamic linker/loader
invocation (e.g., ``/lib64/ld-linux-x86-64.so.2 /path/to/executable``),
the loader executable&#x27;s name is now captured and passed on to ``execvp``
call when restarting the process (``onedir`` mode) or starting the
child process (``onefile`` mode). This ensures that the restarted/spawned
process also uses the specified dynamic loader instead of the one
encoded in executable&#x27;s ELF headers. (:issue:`8662`)
* (Windows) In debug-enabled bootloader variants, copies of debug/warning/error
messages are now submitted to ``OutputDebugString`` win32 API in addition
to their primary output mechanism (i.e., ``stderr`` or message dialog).
This applies to both console and noconsole/windowed bootloader variants.
(Previously, ``OutputDebugString`` was used only for debug messages in
debug-enabled noconsole/windowed bootloader variant, where it serves as
the primary output mechanism.) (:issue:`8642`)
* (Windows) The ``onefile`` parent process now sets up invisible window
to receive and handle ``WM_QUERYENDSESSION`` and ``WM_ENDSESSION``
event messages, which allows it properly clean up temporary files during
session shutdown (i.e., user logging off, or initiating system shutdown
or restart). Cleanup during session shutdown should now work in both
console-enabled and windowed/noconsole builds, and regardless of whether
splash screen is used or not. (:issue:`8648`)
* (Windows) The parent process of a ``onefile`` application with enabled
splash screen now attempts to pre-load a system-wide copy of
``VCRUNTIME140.dll``, preferring it over the bundled copy (which would
be loaded as dependency of Tcl/Tk DLLs during splash screen setup).
If a system-wide copy is available, the OS and/or anti-virus
programs might inject other 3rd party DLLs into the process that
also depend on ``VCRUNTIME140.dll`` (for example, Trend Micro&#x27;s User Mode
Hooking component has been observed to do that). Such externally loaded
DLLs prevent the bootloader from unloading the ``VCRUNTIME140.dll``
during the clean-up phase, and if the bundled copy was loaded, it would
also prevent its removal from the application&#x27;s temporary directory.
(:issue:`8650`)
* Bootloader&#x27;s debug/error/warning messages are now always formatted in
the temporary buffer (even when they are written to ``stderr``), in
order to ensure their atomicity and avoid interleaving of message parts
in multi-process scenarios. (:issue:`8642`)
* Change the prefix of debug/warning/error messages from `[{PID}]` to
`[PYI-{PID}:{SEVERITY}]`, and apply it consistently across all
bootloader-generated messages. (:issue:`8642`)
* Implemented explicit tracking of (sub)process level via newly-introduced
:envvar:`_PYI_PARENT_PROCESS_LEVEL` environment variable. This allows us to
reliably distinguish between different process types: in ``onedir``
applications, between the main application process and worker sub-process(es)
spawned via :data:`sys.executable`; in ``onefile`` applications, between the
parent process, the main application process, and worker sub-process(es)
spawned via :data:`sys.executable`. (:issue:`8634`)
* Reworked the detection of inherited PyInstaller environments, which now has
reversed logic compared to original implementation. Up until now, a process
running the bootloader was considered a (new) top-level process of a frozen
application unless the ``_MEIPASS2`` environment was set. Because bootloader
was clearing the ``_MEIPASS2`` environment variable prior to running the
python code in the main application process, this meant that application&#x27;s
responsibility to restore the ``_MEIPASS2`` environment variable before
spawning worker sub-process via :data:`sys.executable` to, for example,
prevent a onefile application from unpacking itself again. In the new
implementation, the default assumption is that the process is a worker
sub-process of the same (instance of) application, unless the path to
PKG/CArchive has changed (which implies that a different executable is used),
as tracked by newly-introduced :envvar:`_PYI_ARCHIVE_FILE` environment variable.
This means that no additional action is needed to spawn worker sub-processes
via :data:`sys.executable` in multiprocessing scenarios, but on the other hand,
:ref:`attempting to restart the application &lt;independent subprocess&gt;` now
requires :envvar:`PYINSTALLER_RESET_ENVIRONMENT` environment variable to be
set before spawning the new application process. To prevent issues when
launching applications built with older version of PyInstaller as
subprocesses, the ``_MEIPASS2`` environment variable was renamed to
:envvar:`_PYI_APPLICATION_HOME_DIR`; note that this refers to the internally-used
environment variable, and does **not** affect the PyInstaller-specific
``sys._MEIPASS`` attribute. (:issue:`8634`)


Module Loader
~~~~~~~~~~~~~

* The ``PyiFrozenImporter`` has been reworked from being a monolithic
`meta path finder
&lt;https://docs.python.org/3/glossary.html#term-meta-path-finder&gt;`_
(with fused `loader &lt;https://docs.python.org/3/glossary.html#term-loader&gt;`_
part)
into path-instanced `path entry finder
&lt;https://docs.python.org/3/glossary.html#term-path-entry-finder&gt;`_
(with fused loader part), registered with python&#x27;s default
`path based finder
&lt;https://docs.python.org/3/glossary.html#term-path-based-finder&gt;`_.
The new path-instanced design enables proper handling of run-time
:data:`sys.path`
modifications; i.e., modules within the PYZ archive can now be resolved
based on entries in :data:`sys.path` that are anchored to the top-level
application directory (``sys._MEIPASS``). This in turn also facilitates
full support for PEP420 namespace packages that are split across
different :data:`sys.path` locations; both within the PYZ archive, on
filesystem within top-level application directory tree, and/or in
fully-external locations. (:issue:`8695`)


Documentation
~~~~~~~~~~~~~

* Add a note about splash screen suppression to the splash screen
documentation. (:issue:`8634`)
* Extend the Advanced Topics section with new subsection,
:ref:`bootloader environment variables`, which documents all public and
private environment variables used by PyInstaller&#x27;s bootloader.
(:issue:`8634`)
* Extend the Common Issues and Pitfalls section with :ref:`new subsection
&lt;independent subprocess&gt;` that describes the new requirements for launching a
:data:`sys.executable`-based process that is supposed to outlive the current
application process, which includes the application restart scenario.
(:issue:`8634`)

6.9.0

------------------

Bugfix
~~~~~~

* (Windows) Work around the problem with ``libgcc_s_dw2-1.dll`` and
``libwinpthread-1.dll`` DLLs files not being removed from application&#x27;s
temporary directory when building splash-screen-enabled onefile
application with 32-bit msys2/mingw32 environment. (:issue:`8587`)
* (Windows) Work around the problem with ``VCRUNTIME140.dll`` DLL file not
being removed from application&#x27;s temporary directory when building
splash-screen-enabled onefile application with UPX enabled. (:issue:`7106`)
* Re-allow ``hiddenimports`` with hyphenated names during Analysis (was blocked
in v6.8.0) (:issue:`8601`)


Hooks
~~~~~

* Add work-around for incompatibility between ``scipy`` and ``numpy`` 2.0.0
(the ``ModuleNotFoundError: No module named &#x27;numpy.f2py&#x27;`` error).
(:issue:`8622`)
* Update ``django`` hook to account for possibility of the deprecated
``DEFAULT_FILE_STORAGE`` setting being set to ``None``. (:issue:`8633`)
* Update ``scipy`` hooks for compatibility with ``scipy`` 1.14.0.
(:issue:`8622`)


Bootloader
~~~~~~~~~~

* (Windows) Implement last-ditch attempt at force-unloading bundled DLLs
from onefile parent process: if onefile application fails to remove its
temporary directory, it now iterates over all DLLs loaded in the process,
identifies the ones that originate from its temporary directory, and
attempts to force-unload them, before trying to remove the temporary
directory again. This should work around for issues with Tcl/Tk DLLs
used by splash screen, which may load additional DLLs, and fail to
automatically unload them when they are unloaded themselves. (:issue:`8587`)
* Fix the order in which Tcl and Tk shared library are unloaded from the
splash-screen enabled frozen application, to prevent the process from
crashing during application cleanup (observed on Windows). (:issue:`8587`)

6.8.0

------------------

Bugfix
~~~~~~

* (macOS) When running ``codesign`` utility on macOS, use hard-coded absolute
path (``/usr/bin/codesign``) to avoid errors when user has the ``codesign``
from `sigtool &lt;https://github.com/thefloweringash/sigtool&gt;`_ in their
``PATH``. (:issue:`8581`)
* (Windows) When setting up DLL search paths for binary dependency analysis,
consider the directory where python executable is located (i.e.,
``os.path.dirname(sys._base_executable)``) in addition to directory pointed to
by ``sys.base_prefix``, in case the two differ. This fixes discovery of
``python3.dll`` when using python that was locally built from source (i.e.,
using ``PCbuild\build.bat`` script that comes with python&#x27;s source code).
(:issue:`8569`)


Incompatible Changes
~~~~~~~~~~~~~~~~~~~~

* Attempting to do a build whilst inside ``C:\Windows`` is now blocked.
(:issue:`8570`)
* Invalid hiddenimports (e.g. filenames instead of module names) are now a build
error. (:issue:`8570`)


Deprecations
~~~~~~~~~~~~

* Adding a Python environment&#x27;s ``site-packages`` directory to
``pathex``/``--paths`` will be blocked in v7.0 (:issue:`8570`)
* Running PyInstaller with escalated privileges (e.g. using sudo or in a *run as
admin* terminal) will be blocked in v7.0. True admin users will be unaffected.
(:issue:`8570`)


Bootloader
~~~~~~~~~~

* (POSIX) Bootloader now attempts to create the run-time temporary directory
given via :option:`--runtime-tmpdir` option (instead of requiring the
directory to already exist), in order to match the behavior on Windows. A
relative run-time temporary directory is now resolved to an absolute full path
before being used to construct the application&#x27;s temporary directory path.
(:issue:`8557`)
* (Windows) Bootloader now verifies the run-time temporary directory given via
:option:`--runtime-tmpdir` option, and raises an error if either the drive is
invalid or if the directory cannot be created (instead of creating the
application&#x27;s temporary directory in the root of the current drive).
(:issue:`8557`)
* (Windows) Instead of converting bootloader&#x27;s debug and error messages from
UTF-8 to local ANSI codepage and displaying them via ANSI API (e.g.,
``fprintf``, ``DebugMessageA``), the bootloader now attempts to convert those
messages to wide-character strings and displays them via wide-character API
(e.g., ``fwprintf``, ``DebugMessageW``). (:issue:`8557`)
* A major refactor and cleanup of bootloader&#x27;s code. (:issue:`8557`)
* The splash screen resources in ``onefile`` builds are now extracted
into the application&#x27;s temporary directory (instead of being extracted into a
sub-directory within the application&#x27;s temporary directory); therefore, they
are now extracted only once, and are shared with the application itself, if
necessary. (:issue:`8557`)

6.7.0

------------------

Bugfix
~~~~~~

* (POSIX) Fix ``PyInstaller.depend.bindepend.resolve_library_path`` for
cases when ``ldconfig`` cache is not available (e.g., ``musl libc`` on
Alpine Linux). In such cases, the search code now distinguishes between
the case when fully suffixed library name is given (i.e., search for
exact match) and the case when library name has no suffix (i.e., search
for library with matching basename). (:issue:`8422`)
* (Windows) Fix mangling of path to the entry-point script when the script
is in the current working directory, and the path to this directory
contains two or more consecutive ``$`` or ``%`` characters. (:issue:`8434`)


Incompatible Changes
~~~~~~~~~~~~~~~~~~~~

* PyInstaller does not attempt to expand environment variables in paths
given via :option:`--workpath`, :option:`--distpath`, :option:`--specpath`,
and :option:`--additional-hooks-dir` anymore (note that other paths were
never subject to environment variable expansion in the first place).
Expansion of the starting tilde (``~``) into user&#x27;s home directory is
still performed, as a work-around for tilde not being expanded by the
shell when passing arguments as ``--workpath=~/path/abc`` instead of
``--workpath ~/path/abc``. (:issue:`8441`)


Hooks
~~~~~

* Have ``sqlalchemy`` hook collect all dialects and plugins that are
registered via ``sqlalchemy.dialects`` and ``sqlalchemy.plugins``
entry-points. This ensures collection of 3rd party dialects and plugins
that may be available in the build environment (e.g., ``ibm-db-sa``).
(:issue:`8465`)
* The ``pywin32-ctypes`` hook now always collects the
``win32ctypes.core.ctypes``
modules, so that the ``ctypes`` backend is always available (i.e., even
if we also collect the ``cffi`` backend due to availability of ``cffi``
in the build environment). This fixes issues when ``cffi`` ends up
unavailable at run-time in spite of being available in the build environment
at build time (for example, due to explicit exclusion via
:option:`--exclude-module`
option). (:issue:`8544`)
* Update ``pkg_resources`` hook for compatibility with ``setuptools`` v70.0.0
and later (fix ``ModuleNotFoundError: No module named
&#x27;pkg_resources.extern&#x27;``). (:issue:`8554`)

6.6.0

------------------

Features
~~~~~~~~

* (Windows) Implement support for resolving executable&#x27;s true location
when launched via a symbolic link. (:issue:`8300`)
* Implement an option to explicitly specify the bytecode optimization level
for collected python code, independent of the optimization level in the
python process under which PyInstaller is running. At the .spec file level,
this is controlled by optional ``optimize`` argument in the ``Analysis``
constructor. At the CLI level, this is controlled by new
:option:`--optimize` command-line option, which sets the ``optimize``
argument for ``Analysis`` as well as :ref:`interpreter run-time options
&lt;specifying python interpreter options&gt;` in the generated spec file.
See :ref:`bytecode optimization level` for details. (:issue:`8252`)


Bugfix
~~~~~~

* (macOS) Explicitly convert the value of ``version`` argument to ``BUNDLE``
into a string, in order to mitigate cases when user accidentally enters
an integer or a float. The version value ends up being written to
``Info.plist`` as the ``CFBundleShortVersionString`` entry, and if this
entry is not of a string type (for example, is an integer), the
generated .app bundle crashes at start. (:issue:`4466`)
* (Windows) Avoid trying to import ``PySimpleGUI`` in the subprocess that
analyzes dynamic library search modifications made by packages prior to
the binary dependency analysis. When imported for the first time,
``PySimpleGUI`` 5.x displays a &quot;first-run&quot; dialog, which poses a problem
for unattended PyInstaller builds running in a clean environment, for
example, in a CI pipeline. (:issue:`8396`)
* (Windows) Implement a work-around for running PyInstaller under python
process with ``-OO`` (or ``PYTHONOPTIMIZE=2``) with ``cffi`` installed.
We now temporarily disable import of ``cffi`` while importing
``pywin32-ctypes`` in ``PyInstaller.compat`` to ensure that ``ctypes``
backend is always used, as the ``cffi`` backend uses ``pycparser`` and
requires docstrings, which makes it incompatible with the ``-OO`` mode.
(:issue:`6345`)


Hooks
~~~~~

* Update ``PySide6.Qt3DRender`` hook for compatibility with ``PySide6``
6.7.0 (add hidden import for ``PySide6.QtOpenGL`` module). (:issue:`8404`)
* Update ``scipy.special._ufuncs`` hook for compatibility with SciPy 1.13.0
(add ``scipy.special._cdflib`` to hidden imports). (:issue:`8394`)


Bootloader
~~~~~~~~~~

* (Windows) Attempt to shorten the duration of spinning-wheel cursor when
launching applications built in ``windowed`` / ``noconsole`` mode.
(:issue:`8359`)


Documentation
~~~~~~~~~~~~~

* Add a new documentation section, :ref:`bytecode optimization level`,
which the describes the new canonical way to control bytecode
optimization level of the collected python code. (:issue:`8252`)
* Add a note to :ref:`specifying python interpreter options` to inform
user that setting the optimization level to the application&#x27;s embedded
python interpreter by itself does not result in bytecode optimization of
modules that have been collected in byte-compiled form (i.e., the majority
of them). (:issue:`8252`)

6.5.0

------------------

Features
~~~~~~~~

* (Linux) Extend the mechanism for collection of ``.hmac`` files from
:issue:`8288` to ``.chk`` files that are used by NSS libraries.
(:issue:`8315`)


Bugfix
~~~~~~

* (Linux) Fix collection of ``QtWebEngineProcess`` helper when collecting
Qt (and ``PySide``/``PyQt`` bindings) installed via Linux distribution
packages. In such scenarios, we now force collection of the helper
executable into ``libexec`` directory inside the Qt sub-directory of
the bindings&#x27; package directory, in order to match the PyPI wheel layout.
(:issue:`8315`)
* (Linux) Fix regression that caused :func:`locale.getlocale` in
frozen applications created with PyInstaller v6.x to return ``(None, None)``
instead of user-preferred locale. (:issue:`8306`)
* (Windows) Avoid trying to import ``pyqtgraph.canvas`` in the subprocess
that analyzes dynamic library search modifications made by packages prior
to the binary dependency analysis. Trying to import ``pyqtgraph.canvas``
causes python interpreter to crash under certain circumstances (the
issue is present in ``pyqtgraph`` &lt;= 0.13.3). (:issue:`8322`)
* (Windows) Fix collection of ``QtWebEngineProcess`` helper when
collecting ``PySide2`` and Qt installed via Anaconda on Windows.
The helper executable is now collected into top-level ``PySide2``
package directory, in order to match the PyPI wheel layout. (:issue:`8315`)
* (Windows) Suppress warnings about unresolvable UCRT DLLs
(``api-ms-win-*.dll``) on Windows 11. (:issue:`8339`)
* Fix bootloaders not being found when running an Intel build of Python on
Windows ARM64. (:issue:`8219`)


Incompatible Changes
~~~~~~~~~~~~~~~~~~~~

* PyInstaller now explicitly disallows attempts to collect multiple Qt
bindings packages (``PySide2``, ``PySide6``, ``PyQt5``, ``PyQt6``) into
a frozen application. When hooks for more than one top-level Qt bindings
package are executed, the build process is aborted with error message.
This restriction applies across all instances of ``Analysis`` within
a single build (i.e., a single .spec file).

If you encounter build errors caused by this new restriction, either
clean up your build environment (remove the bindings that you are not
using), or explicitly exclude the extraneous bindings using
:option:`--exclude-module`
(or equivalent ``excludes`` list passed as argument to ``Analysis`` in
the .spec file).

The automatic exclusion of extraneous bindings needs to be done via hooks on
per-package basis, so please `report problematic packages
&lt;https://github.com/pyinstaller/pyinstaller-hooks-contrib/issues&gt;`_ so that we
can write hooks for them. (:issue:`8329`)


Hooks
~~~~~

* (Linux) When searching for dynamically-loaded NSS libraries during
collection of ``QtWebEnginge``, account for the possibility of said
libraries being either in a separate ``nss`` directory or in the main
library directory. This fixes problems with missing NSS libraries on
contemporary Linux distributions that do not use separate ``nss``
directory (anymore). (:issue:`8315`)
* Add a hook for ``pandas.io.clipboard`` to exclude the conditional
import of ``PyQt5`` from this module; the module primarily uses ``qtpy``
as its Qt bindings abstraction, and the conditional import of ``PyQt5``
interferes with Qt bindings selection done by our ``qtpy`` hook.
(:issue:`8329`)
* Add hook for ``qtpy`` to prevent collection of multiple available Qt
bindings. The hook attempts to select a single Qt bindings package
and exclude all other Qt bindings packages with the help of the
``PyInstaller.utils.hooks.qt.exclude_extraneous_qt_bindings``
helper. (:issue:`8329`)
* Extend hooks for ``matplotlib`` to prevent collection of multiple
available Qt bindings. The new hook for ``matplotlib.backends.qt_compat``
attempts to select a single Qt bindings package via the following
logic implemented in the
``PyInstaller.utils.hooks.qt.exclude_extraneous_qt_bindings``
helper: first, we check if hooks for any Qt bindings package have already
been run; if they had, those bindings are selected. If not, we check for
user-specified bindings in the ``QT_API`` environment variable; if valid
bindings name is specified, those bindings are selected. Otherwise, we
select one of available bindings. Once a Qt bindings package is selected,
the imports of all other Qt bindings packages are excluded from the
hooked package. (:issue:`8329`)
* Have run-time hooks for Qt bindings (``PySide2``, ``PySide6``, ``PyQt5``,
and ``PyQt6``) check for presence of the embedded ``:/qt/etc/qt.conf``
resource, and if not present, inject their own version. This
aims to ensure that the bundled Qt is always relocatable, even if the
package does not perform injection of embedded ``qt.conf`` file (most
notably, this seems to be the case with ``PySide2`` collected from
Linux distribution packages, and ``PySide2`` collected from Anaconda
on Windows, Linux, and macOS). (:issue:`8315`)
* PyInstaller now explicitly disallows attempts to collect multiple Qt
bindings packages (``PySide2``, ``PySide6``, ``PyQt5``, ``PyQt6``) into
a frozen application. When hooks for more than one top-level Qt bindings
package are executed, the build process is aborted with error message
that informs user of the situation and what to do about it (i.e., exclusion
of extraneous packages). The limitation applies to all analyses within a
spec file. (:issue:`8329`)
* Remove run-time hook for ``win32com``, as per discussion in issue:`8309`.
(:issue:`8313`)
* Update hook for ``matplotlib.backends`` to include ``QtAgg`` and ``Gtk4Agg``
in the list of backend candidates. (:issue:`8334`)


Bootloader
~~~~~~~~~~

* Have bootloader set the ``configure_locale`` field in the interpreter
pre-config structure, so that user-preferred locale is set during
interpreter pre-initialization. (:issue:`8306`)


Bootloader build
~~~~~~~~~~~~~~~~

* The target architecture on Windows using MSVC now defaults to that of the
current Python environment – not the current OS. (:issue:`8219`)

6.4.0

------------------

Features
~~~~~~~~

* (Linux) Collect ``.hmac`` files accompanying shared libraries, if such files
are available. This allows frozen application to run on FIPS-enabled Red Hat
Enterprise systems, where HMAC is required by self-check implemented by the
OpenSSL crypto library. Furthermore, ensure that shared libraries with
accompanying ``.hmac`` files are exempted from any additional processing (for
example, when building with :option:`--strip` option) to avoid invalidating
the HMAC. (:issue:`8273`)
* (Windows) Make bootloader codepaths involved in creation of temporary
directories for ``onefile`` builds AppContainer-aware. If the process runs
inside an AppContainer, the temporary directory&#x27;s DACL needs to explicitly
include the AppContainerSID, otherwise the directory becomes inaccessible to
the process. (:issue:`8291`)
* (Windows) Make Windows implementation of PyInstaller&#x27;s
``_pyi_rth_utils.tempdir.secure_mkdir`` (used by ``matplotlib`` and
``win32com`` run-time hooks to create temporary directories)
AppContainer-aware. If the process runs inside an AppContainer, the temporary
directory&#x27;s DACL needs to explicitly include the AppContainerSID, otherwise
the directory becomes inaccessible to the process. (:issue:`8290`)
* Implement strict Qt dependency validation for collection of Qt plugins and QML
components/plugins. We now perform preliminary binary dependency analysis of
the plugins, and automatically exclude plugins that have at least one missing
Qt dependency. This prevents collection of plugins that cannot be used anyway
because of a missing Qt shared library (that is, for example, omitted from a
PyPI wheel). Furthermore, we disallow Qt dependencies of a plugin to be
resolved outside of the primary location of Qt shared libraries, in order to
prevent missing dependencies from pulling in Qt libraries from alternative
locations that happen to be in the search path (for example, when using
``PyQt5`` PyPI wheels while also having a system-installed Qt5 on Linux, a
Homebrew-installed Qt5 on macOS, or a custom Windows Qt5 build that happens to
be in ``PATH``). (:issue:`8226`)


Bugfix
~~~~~~

* (Linux) Prevent collection of ``libcuda.so.1``, which is part of NVIDIA
driver and must match the rest of the driver&#x27;s components. Collecting
a copy might lead to issues when build and target system use different
versions of NVIDIA driver. (:issue:`8278`)
* (macOS) When validating the macOS SDK version of collected binaries,
handle errors raised by ``osxutils.get_macos_sdk_version``; log a
warning about failed version query, and add the offending binary to
the list of potentially problematic binaries to warn the user about.
(:issue:`8220`)
* Fix ``pkgutil.iter_modules`` override to gracefully handle cases when
the given path corresponds to a module instead of a package. (:issue:`8191`)
* Prevent Qt and QML plugins with missing Qt dependencies in the
``PySide2``, ``PyQt5``, ``PySide6``, and ``PyQt6`` PyPI wheels from
pulling in Qt shared libraries from alternative locations (for example,
system-installed Qt on Linux, Homebrew-installed Qt on macOS, or
a custom Windows Qt build that happens to be in ``PATH``), and resulting
in a frozen application that contains an incompatible mix of Qt libraries.
(:issue:`8087`)
* Switch the hashing function in PyInstaller&#x27;s binary cache from MD5 to
SHA1, as the former cannot be used on FIPS-enabled Red Hat Enterprise
Linux systems. (:issue:`8288`)
* When trying to run ``pyinstaller`` (or equivalent ``python -m PyInstaller``)
against non-existing script file(s), exit immediately - without trying
to write the .spec file and building it. This prevents us from overwriting
an existing (and customized) .spec file if user makes a typo in the .spec
file&#x27;s suffix when trying to build it, for example, ``pyinstaller
program.spec``. (:issue:`8279`)


Hooks
~~~~~

* (macOS) Have ``PySide6`` and ``PyQt6`` run-time hooks prepend
``sys._MEIPASS`` to ``DYLD_LIBRARY_PATH`` in POSIX builds, in order
to ensure that ``QtNetwork`` discovers the bundled copy of the OpenSSL
shared library. (:issue:`8226`)
* Extend the OpenSSL shared library collection in the ``QtNetwork`` hook
helper for ``PySide2``, ``PyQt5``, ``PySide6``, and ``PyQt6`` to
cover all applicable versions of OpenSSL (1.0.2, 1.1.x, 3.x). In
a

Update pyinstaller from 5.9.0 to 6.20.0

4f36532

pyup-bot mentioned this pull request Apr 22, 2026

Update pyinstaller to 6.19.0 #229

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update pyinstaller to 6.20.0#235

Update pyinstaller to 6.20.0#235
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-pyinstaller-5.9.0-to-6.20.0

pyup-bot commented Apr 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

pyup-bot commented Apr 22, 2026

6.20.0

6.19.0

6.18.0

6.17.0

6.16.0

6.15.0

6.14.2

6.14.1

6.14.0

6.13.0

6.12.0

6.11.1

6.11.0

6.10.0

6.9.0

6.8.0

6.7.0

6.6.0

6.5.0

6.4.0

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant