Project History¶
Work on PyOxidizer started in November 2018 by Gregory Szorc.
Blog Posts¶
Building Standalone Python Applications with PyOxidizer (2019-06-23)
PyOxidizer Support for Windows (2019-01-06)
Faster In-Memory Python Module Importing (2018-12-28)
Distributing Standalone Python Applications (2018-12-18)
Version History¶
0.2.0¶
Released on June 30, 2019.
Backwards Compatibility Notes¶
Applications are now built into an
apps/<appname>/(debug|release)directory instead ofapps/<appname>. This allows debug and release builds to exist side-by-side.
Bug Fixes¶
Extracted
.eggdirectories in Python package directories should now have their resources detected properly and not as Python packages with the name*.egg.site-packagesdirectories are now recognized as Python resource package roots and no longer have their contents packaged under asite-packagesPython package.
New Features¶
Support for building and embedding C extensions on Windows, Linux, and macOS in many circumstances. See Native Extension Modules for support status.
pyoxidizer initnow accepts a--pip-installoption to pre-configure generatedpyoxidizer.tomlfiles with packages to install viapip. Combined with the--python-codeoption, it is now possible to createpyoxidizer.tomlfiles for a ready-to-use Python application!pyoxidizernow accepts a--verboseflag to make operations more verbose. Various low-level output is no longer printed by default and requires--verboseto see.
All Other Relevant Changes¶
Packaging now automatically creates empty modules for missing parent packages. This prevents a module from being packaged without its parent. This could occur with namespace packages, for example.
pip-install-simplerule now passes--no-binary :all:to pip.Cargo packages updated to latest versions.
0.1.3¶
Released on June 29, 2019.
Bug Fixes¶
Fix Python refcounting bug involving call to
PyImport_AddModule()whenmode = moduleevaluation mode is used. The bug would likely lead to a segfault when destroying the Python interpreter. (#31)Various functionality will no longer fail when running
pyoxidizerfrom a Git repository that isn’t the canonicalPyOxidizerrepository. (#34)
New Features¶
pyoxidizer initnow accepts a--python-codeoption to control which Python code is evaluated in the produced executable. This can be used to create applications that do not run a Python REPL by default.pip-install-simplepackaging rule now supportsexcludesfor excluding resources from packaging. (#21)pip-install-simplepackaging rule now supportsextra_argsfor adding parameters to the pip install command. (#42)
All Relevant Changes¶
Minimum Rust version decreased to 1.31 (the first Rust 2018 release). (#24)
Added CI powered by Azure Pipelines. (#45)
Comments in auto-generated
pyoxidizer.tomlhave been tweaked to improve understanding. (#29)
0.1.2¶
Released on June 25, 2019.
Bug Fixes¶
Honor
HTTP_PROXYandHTTPS_PROXYenvironment variables when downloading Python distributions. (#15)Handle BOM when compiling Python source files to bytecode. (#13)
All Relevant Changes¶
pyoxidizernow verifies the minimum Rust version meets requirements before building.
0.1.1¶
Released on June 24, 2019.
Bug Fixes¶
pyoxidizerbinaries built from crates should now properly refer to an appropriate commit/tag in PyOxidizer’s canonical Git repository in auto-generatedCargo.tomlfiles. (#11)
0.1¶
Released on June 24, 2019. This is the initial formal release of PyOxidizer.
The first pyoxidizer crate was published to crates.io.
New Features¶
Support for building standalone, single file executables embedding Python for 64-bit Windows, macOS, and Linux.
Support for importing Python modules from memory using zero-copy.
Basic Python packaging support.
Support for jemalloc as Python’s memory allocator.
pyoxidizerCLI command with basic support for managing project lifecycle.