maketool
maketool is a command-line utility and helper module that simplifies execution and building PySide6 Python 3.7+ applications into executables using PyInstaller 5.8.0. Note: Windows only
It's especially useful for GUI projects that need embedded resources (e.g., .ui, .qrc) and aim to produce portable .exe builds with minimal setup.
Why Use maketool?
If you build windows desktop apps using PySide6, maketool:
- Saves time when converting
.uiand.qrcfiles - Simplifies PyInstaller builds
- Packages your application with minimal commands
- Automates repetitive tasks like building and cleanup
- Integrates easily with
.batscripts or shell commands - Is great for both beginners and advanced developers using PySide6
Commands
1. run
Purpose: Compile .ui and .qrc files recursively (using pyside6-uic.exe and pyside6-rcc.exe), then run the Python program using pythonw.exe.
Note: it will ONLY rebuild pyside components that are out of date, so that execution is fast as possible, yet always includes any changes. FYI: python program is run with pythonw.exe so that the terminal window does not appear.
usage: maketool-run [-h] file
parameters:
file python file to run
parameters:
-h, --help show this help message and exit
2. clean
Purpose: Remove build artifacts, caches, generated UI files, PyInstaller output, and spec files.
__pycache__folders*_ui.py,*_rc.py,*.pyc,*.pyo- PyInstaller
build/anddist/folders .specfiles in the current directory
Run it like this:
maketool-clean
3. compile
Purpose: Build an executable using PyInstaller, including UI/QRC compilation, icon embedding, version stamping, and resource embedding.
-
Supports onefile/onedir/console modes.
-
AutoGenerates a PyInstaller
.specfile -
Handles .ui/.qrc compilation automatically.
-
Supports embedding arbitrary files which is useful for DLLs or data assets.
-
Runs PyInstaller with the provided options
-
Updates version if exists in python file with --version value if provided
usage: maketool-compile [-h] --file FILE --type {onefile,onedir,console} [--icon=ICON] [--embed=EMBED] [--version=VERSION]
parameters:
-h, --help show this help message and exit
--file FILE python file to compile to exe
--type {onefile,onedir,console}
type of exe to build
--icon ICON ico file
--embed EMBED comma delimited list of files to embed
--version VERSION program version (otherwise use __version__ in py source)
4. sublime
WARNING: This will overwrite existing custom key bindings at that path Purpose: Install custom Sublime Text 4 shortcuts and commands. Future: plan for support of vscode editor.
CTRL+BACKSPACE - delete line CTRL+ALT+E - open windows explorer where current file is located CTRL+0 - reset font size F1 - insert print statement for variable where cursor is located F5 - run pyflakes on current python source F6 - maketool-refscan - scan for unused/orphan files in the project F7 - build (runs maketool-run on current script via the build system) F10 - insert current date/day
usage: maketool-sublime [-h] --path PATH
parameters:
-h, --help show this help message and exit
--path PATH sublime text - data/package/user path
5. refscan
Purpose: Scan for unused/orphan files using string-based heuristics.
This is especially useful for catching forgotten assets like .ui, .qss, .ico, images, etc.
"Unused" means "no string reference found anywhere in .py files".
Default behavior is unused only:
maketool-refscan
Show both used and unused:
maketool-refscan --show-used
Write a CSV report:
maketool-refscan --csv refscan-report.csv
Notes:
- This is heuristic (string-based). It may miss dynamically constructed paths/imports and may produce false positives.
- For best results, run it from your project root.
Features
- Simple command-line interface for
.bator.shworkflows - Converts all
.uiand.qrcfiles recursively - Cleans up Python build artifacts
- Packages apps using PyInstaller
- Supports custom
.icoicons - Supports optional resource embedding
Requirements
Installation
Install maketool helper from PyPI with following command:
pip install maketool
License
MIT License
Copyright 2026 Alan Lilly
Metadata
Release files for maketool 0.8.30
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 |
|---|---|---|---|---|
| maketool-0.8.30.tar.gz | 18.6 kB | Without provenance | Details for maketool-0.8.30.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| maketool-0.8.30-py3-none-any.whl | Python 3 | none | any | Details for maketool-0.8.30-py3-none-any.whl |
Total release size: 37.6 kB
Release files / maketool-0.8.30.tar.gz
| Download URL | maketool-0.8.30.tar.gz |
|---|---|
| Size | 18.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c5ddb6addcbebbd84d216c2d4fb1a44eae081946c129939860e1435ecbe9464
|
|
BLAKE2b-256 checksum How to use checksums |
13eb5688c1a0e68e4724a11d25b57af00a801b63098b5f1067fdbd5b3c6309ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Release files / maketool-0.8.30-py3-none-any.whl
| Download URL | maketool-0.8.30-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
70200cdde05fb6bf1558b1c21a6d71e07e7bd652b6f17b8f8867f86b440c05f8
|
|
BLAKE2b-256 checksum How to use checksums |
2637197ff2d02c9b5db23764bfe7651580fc6b7f849a942c856dea81494ff495
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Security for maketool 0.8.30
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.