PyOxidizer¶
PyOxidizer
is a utility that aims to solve the problem of how
to distribute Python applications. See Overview for more or
dive into Getting Started to learn how to start using
PyOxidizer
.
The official home of the PyOxidizer
project is
https://github.com/indygreg/PyOxidizer. Official documentation lives
at Read The Docs
(unreleased/latest commit,
last release).
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 or via PayPal.
The creator and maintainer of PyOxidizer
is
Gregory Szorc.
- Overview
- Getting Started
- The
pyoxidizer
Command Line Tool- Settings
- Creating New Projects with
init-config-file
- Creating New Rust Projects with
init-rust-project
- Adding PyOxidizer to an Existing Project with
add
- Building PyObject Projects with
build
- Running the Result of Building with
run
- Analyzing Produced Binaries with
analyze
- Inspecting Python Distributions
- Debugging Resource Scanning and Identification with
find-resources
- Defining Extra Variables in Starlark Environment
- Configuration Files
- Automatic File Location Strategy
- Concepts
- Resource Attributes Influencing Adding
- Global Symbols
- Functions for Manipulating Global State
- Functions for Managing Targets
- Extensions to Tugger’s Starlark Dialect
File
PythonDistribution
PythonEmbeddedResources
PythonExecutable
PythonExtensionModule
PythonInterpreterConfig
PythonModuleSource
PythonPackageResource
PythonPackageDistributionResource
PythonPackagingPolicy
- Packaging User Guide
- Creating a PyOxidizer Project
- Packaging Primitives in
pyoxidizer.bzl
Files - Understanding Python Distributions
- Managing How Resources are Added
- Packaging Python Files
- Packaging Files Instead of In-Memory Resources
- Working with Python Extension Modules
- Managing Packed Resources Data
- Trimming Unused Resources
- Performance of Built Binaries
- Packaging Pitfalls
- Masquerading As Other Packaging Tools
- Standalone / Single File Applications with Static Linking
- Licensing Considerations
- Terminfo Database
- Using the
multiprocessing
Python Module - SSL Certificate Loading
- Using the
tkinter
Python Module - Building an Executable that Behaves Like
python
- Distributing User Guide
oxidized_importer
Python Extension- Getting Started
- Python Meta Path Finders
OxidizedFinder
Meta Path FinderOxidizedFinder
Behavior and Complianceoxidized_importer
Python Resource Types- Resource Scanning APIs
- Loading Resource Files
- Freezing Applications with
oxidized_importer
- Common Issues
- Security Implications of Loading Resources
- API Reference
- Python Packed Resources
- The
pyembed
Rust Crate - PyOxidizer for Rust Developers
- Shipping Applications with
tugger
- Frequently Asked Questions
- Where Can I Report Bugs / Send Feedback / Request Features?
- Why Build Another Python Application Packaging Tool?
- Can Python 2.7 Be Supported?
- Why is Python 3.8 Required?
No python interpreter found of version 3.*
Error When Building- Why Rust?
- Why is the Rust Code… Not Great?
- What is the Magic Sauce That Makes PyOxidizer Special?
- Can Applications Import Python Modules from the Filesystem?
error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
When Buildingvcruntime140.dll was not found
Error on Windowsld: unsupported tapi file type '!tapi-tbd' in YAML file
on macOS When Building
- Project Status
- Comparisons to Other Tools
- Contributing to PyOxidizer
- Project History
- Technical Notes