maxson-build-utils
Centralized org tooling for PyInstaller, DMG, AppImage, DEB, PYZ, etc.
A convention-optional build and deployment framework, with an opinionated Maxson project scaffold available as a convenience.
The central secret sauce is argument and variable value routing from disk. Icons, references, descriptions, names, paths, it can all be inferred or drawn. We leverage the .persist file where necessary to achieve this but ideally we draw values from the pyproject.toml file and form other expected standard paths.
In this way, wrapped CLI tools like create-dmg or pyonstaller can instead draw in determinstic argument values instead of requiring explicit flags.
Package scaffolding precedes building in most cases, so that manifest files are available.
If you frequently build and distribute Python applications and find yourself repeating the same configuration steps, this tool can significantly accelerate your development and simplify the long-term maintenance of your projects.
Spotlight IT
ChatGPT or Gemini can provide good Python core logic. "Fix my problem, tell me the library, write a single script, give me some functions with some arguments."
But how do you run that solution on other computers? For coworkers? For contractors?
maxson-build-utils provides you with an opinionated canvas. Drop in your special core, wire up the args in the functions to the CLI and the GUI, run the builds, and then you've got a one way ticket to the Windows store. IT will probably say yes.
Shadow IT? No, Spotlight IT
Installation
pipx install "maxson-build-utils[pyinstaller]"
Quick Start
Scaffold and edit a new project
mkdir my-project
cd my-project
mbu init all
# edit core.py with special logic
# edit cli.py and gui.py to expose core features
# edit pyproject.toml to add new dependecies
# sync the local new venv
uv sync --group dev --extra gui --extra pyinstaller
Build local artifacts
mbu build shiv
mbu build pyinstaller
Leverage the batteries-included github runners by pushing to github. This will give you files that may be submitted to the Windows Store, the Apple store, and Linux distribution.
git tag v0.1.0
git push origin v0.1.0
# Runners are designed to build and upload artifacts to the release.
gh release create v0.1.0 --title "my-project v0.1.0"
Helptree
See the maxson-build-utils Typer CLI structure.
maxson-build-utils helptree
1 maintainer
Release files for maxson-build-utils 0.1.42
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| maxson_build_utils-0.1.42.tar.gz | 451.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| maxson_build_utils-0.1.42-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 935.2 kB
Release files / maxson_build_utils-0.1.42.tar.gz
| Download URL | maxson_build_utils-0.1.42.tar.gz |
|---|---|
| Size | 451.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83aa3735a216f552c185e3c046bed4f8ea03f93db36ca4c6ce4f28d9ba23d35d
|
|
BLAKE2b-256 checksum How to use checksums |
24cc7031a1385acbdcf2a60348570910821139da3d79ec5d72271a03b86daef6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / maxson_build_utils-0.1.42-py3-none-any.whl
| Download URL | maxson_build_utils-0.1.42-py3-none-any.whl |
|---|---|
| Size | 483.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
984dbbc1600f9bc78fa45f9936d72fd092b001318693efa419991b5fd212531e
|
|
BLAKE2b-256 checksum How to use checksums |
ec1bd4e2c22f70be47be90d46a34e0400a26833d2a6ea7326df807ac46db03b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log
