Releases: indygreg/PyOxidizer
0.6.0
This is a relatively minor release. The full changelog is at https://pyoxidizer.readthedocs.io/en/stable/history.html#version-0-6-0.
Meaningful changes in this release are:
- The
pyembed
crate is now published on crates.io and can be used like any other crate. - We now use the upstream
cpython
crate instead of a fork of it. - Embedded Python interpreters can now be configured to run a file (in addition to executing code, a module, etc).
This release also lays the groundwork for different Python distribution flavors. The goal of this work is to support other Python distribution types instead of the highly opinionated statically linked distributions we currently require. For example, we want to eventually support using existing Python distributions discovered from the filesystem as well as distributions that use more traditional dynamic linking. These features will materialize in a future release.
0.5.0
This release of PyOxidizer is significant rewrite of the previous version.
The impetus for the rewrite is to transition from TOML to Starlark
configuration files. The new configuration file format should allow
vastly greater flexibility for building applications and will unlock a
world of new possibilities.
The transition to Starlark configuration files represented a shift from
static configuration to something more dynamic. This required refactoring
a ton of code.
As part of refactoring code, we took the opportunity to shore up lots
of the code base. PyOxidizer was the project author's first real Rust
project and a lot of bad practices (such as use of .unwrap()
/panics)
were prevalent. The code mostly now has proper error handling. Another
new addition to the code is unit tests. While coverage still isn't
great, we now have tests performing meaningful packaging activities.
So regressions should hopefully be less common going forward.
Because of the scale of the rewritten code in this release, it is expected
that there are tons of bugs of regressions. This will likely be a transitional
release with a more robust release to follow.