pep723-to-wheel
A small utility for converting PEP 723 inline dependency scripts into wheels and reconstructing scripts from wheels. Especially useful for taking reproducible Marimo notebooks to production environments.
CLI
Build a wheel from a script that has a PEP 723 inline block:
pep723-to-wheel build path/to/script.py --output-dir dist
Set an explicit wheel version (defaults to calendar versioning using the script mtime as the patch segment):
pep723-to-wheel build path/to/script.py --version 2024.12.25
Reconstruct a script from a wheel or package name:
pep723-to-wheel import path/to/package.whl --output reconstructed.py
pep723-to-wheel import requests --output reconstructed.py
Library
from pathlib import Path
from pep723_to_wheel import build_script_to_wheel, import_wheel_to_script
result = build_script_to_wheel(Path("script.py"))
print(result.wheel_path)
import_result = import_wheel_to_script("requests", Path("reconstructed.py"))
print(import_result.script_path)
Development
make test
make typecheck
make ruff
Release process
Releases are automated on pushes to main by the CD workflow in .github/workflows/cd.yml.
- The workflow determines the latest
v*Git tag and runs.github/workflows/cd_version.pyto resolve the next version. If the latest tag matches the current major/minor, it bumps the patch to one higher than the max of the current patch and the tag patch. - If
pyproject.tomlchanges, the workflow commits the version bump back tomain. - It tags the release as
v<version>, builds the wheel withuv build --wheel, publishes to PyPI, and creates a GitHub release with the wheel attached.
To trigger a release, merge or push changes to main and ensure PYPI_API_TOKEN is configured in
the repository secrets.
Metadata
Release files for pep723-to-wheel 0.1.3
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 | Actions |
|---|---|---|---|---|
| pep723_to_wheel-0.1.3.tar.gz | 35.2 kB | Without provenance | Details for pep723_to_wheel-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pep723_to_wheel-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for pep723_to_wheel-0.1.3-py3-none-any.whl |
Total release size: 43.3 kB
Release files / pep723_to_wheel-0.1.3.tar.gz
| Download URL | pep723_to_wheel-0.1.3.tar.gz |
|---|---|
| Size | 35.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c815a11ebb657ed3f6e4fb47b7dd12c365dda399d46045f06a331d54afff4cb
|
|
BLAKE2b-256 checksum How to use checksums |
ed4beba8f140b6d440bc1439064efbce04c3904c82d770e0d5c7f20f488b9327
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pep723_to_wheel-0.1.3-py3-none-any.whl
| Download URL | pep723_to_wheel-0.1.3-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f9d6f1787c5c116bcfb81de65de59f089a692f4572e6d6cea00ea0f7dd609a0
|
|
BLAKE2b-256 checksum How to use checksums |
297be4b4759158e4ae1879acc7fa4e756e8c57ece409887d3d9af8962412999b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pep723-to-wheel 0.1.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.