Overview
bdist_pyinstaller is a side-car distutils command to automate creation of the pyinstaller packages in a non-intrusive way.
The problem dist_pyinstaller is trying to solve
The application written in Python is never directly executed natively. Similarly to Java, Python code is compiled into a byte code(opcode) and it's running on a Python VM.
As a consequence, to run anything written in Python one needs to have an installation of Python compiler+VM.
It usually comes as OS-dependent package(rpm, deb etc.) or it can be compiled from source.
Furthermore, despite having a very rich core libraries at their disposal, Python programs often need to pull some 3rd party packages in. Some packages require libraries which have to be pre-installed on the OS level.
This would require the combination of:
- Internet connection or setting up the equivalent repositories holding the packages
- Priviledge escalation if the installation of python and/or extra packages is to be treated as a system-wide one
- An extra care when dealing with version upgrades(both python itself as well as the packages) as various applications often come with conflicting requirements which are not straight forward to solve on a shared platform.
There are solutions to all these problems, but they all come with the extra complexity, reduced reliability and maintanance cost when the aim is to have simple and stable way of executing a given program/utility.
bdist_installer offers a very simple path from a well defined Python utility to a single binary with all the required bits frozen-in. That includes the Python runtime. Thanks to pyinstaller used behind the scenes it is very powerful, yet still very simple in non-trivial use-cases.
Table of Contents
Metadata
Release files for bdist-pyinstaller 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| bdist_pyinstaller-0.2.1.tar.gz | 14.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bdist_pyinstaller-0.2.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 28.1 kB
Release files / bdist_pyinstaller-0.2.1.tar.gz
| Download URL | bdist_pyinstaller-0.2.1.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24945cf2c3284288e3ac3fb79d8ca6cc590fa0f2add55bda7c1bd7bde573cad5
|
|
BLAKE2b-256 checksum How to use checksums |
772ef4508bf7e3f6e6505c457b67ff5541fe8991e475f03a69e5808b7eb01029
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Release files / bdist_pyinstaller-0.2.1-py2.py3-none-any.whl
| Download URL | bdist_pyinstaller-0.2.1-py2.py3-none-any.whl |
|---|---|
| Size | 13.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
2e5bd3d5f525fde5c048e47caf16dfa4c7f9cca10c2ba6468fb304dbe0f4abb2
|
|
BLAKE2b-256 checksum How to use checksums |
69d163ad525612ca137192753c095da28e10ebbebf3d0193a7bc6595c46a54bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Security for bdist-pyinstaller 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.