bin+lib pyoxidizer

Package self-contained Python applications

11 releases (6 breaking)

✓ Uses Rust 2018 edition

0.7.0 Apr 10, 2020
0.6.0 Feb 13, 2020
0.5.1 Jan 27, 2020
0.4.0 Oct 28, 2019
0.1.3 Jun 29, 2019

#23 in #python

Download history 94/week @ 2020-03-16 96/week @ 2020-03-23 62/week @ 2020-03-30 152/week @ 2020-04-06 153/week @ 2020-04-13 104/week @ 2020-04-20 88/week @ 2020-04-27 120/week @ 2020-05-04 147/week @ 2020-05-11 78/week @ 2020-05-18 92/week @ 2020-05-25 116/week @ 2020-06-01 93/week @ 2020-06-08 139/week @ 2020-06-15 120/week @ 2020-06-22 79/week @ 2020-06-29

455 downloads per month

MPL-2.0 license

19K SLoC

Rust 16K SLoC // 0.1% comments Python 3K SLoC // 0.3% comments


Build Status

PyOxidizer is a utility for producing binaries that embed Python. The over-arching goal of PyOxidizer is to make complex packaging and distribution problems simple so application maintainers can focus on building applications instead of toiling with build systems and packaging tools.

PyOxidizer is capable of producing a single file executable - with a copy of Python and all its dependencies statically linked and all resources (like .pyc files) embedded in the executable. You can copy a single executable file to another machine and run a Python application contained within. It just works.

PyOxidizer exposes its lower level functionality for embedding self-contained Python interpreters as a tool and software library. So if you don't want to ship executables that only consist of a Python application, you can still use PyOxidizer to e.g. produce a library containing Python suitable for linking in any application or use PyOxidizer's embedding library directly for embedding Python in a larger application.

The Oxidizer part of the name comes from Rust: executables produced by PyOxidizer are compiled from Rust and Rust code is responsible for managing the embedded Python interpreter and all its operations. If you don't know Rust, that's OK: PyOxidizer tries to make the existence of Rust nearly invisible to end-users.

While solving packaging and distribution problems is the primary goal of PyOxidizer, a side-effect of solving that problem with Rust is that PyOxidizer can serve as a bridge between these two languages. PyOxidizer can be used to easily add a Python interpreter to any Rust project. But the opposite is also true: PyOxidizer can also be used to add Rust to Python. Using PyOxidizer, you could bootstrap a new Rust project which contains an embedded version of Python and your application. Initially, your project is a few lines of Rust that instantiates a Python interpreter and runs Python code. Over time, functionality could be (re)written in Rust and your previously Python-only project could leverage Rust and its diverse ecosystem. Since PyOxidizer abstracts the Python interpreter away, this could all be invisible to end-users: you could rewrite an application from Python to Rust and people may not even know because they never see a libpython, .py files, etc.

Project Info

🏠 The official home of the PyOxidizer project is https://github.com/indygreg/PyOxidizer.

📔 Documentation (generated from the docs/ directory) is available at https://pyoxidizer.readthedocs.io/en/latest/index.html.

💬 The pyoxidizer-users mailing list is a forum for users to discuss all things PyOxidizer.

💰 If you want to financially contribute to PyOxidizer, do so on Patreon.


~819K SLoC