mc10-tools
This is a simple collection of tools to assist with developing software for the TRS-80 Microcolor Computer MC-10.
Installation
git clone https://github.com/jamieleecho/mc10-tools.git
cd mc10-tools
make install-pre-commit
make install
Tools
c10tobas
Usage: c10tobas [OPTIONS] INPUT_FILE OUTPUT_FILE
Extract and detokenizes the *.bas file in INPUT_FILE and stores it in
OUTPUT_FILE
Options:
--version Show the version and exit.
--help Show this message and exit.
bastoc10
Usage: bastoc10 [OPTIONS] INPUT_FILE OUTPUT_FILE
Tokenizes the given *.bas file specified byt INPUT_FILE, outputing the
result into a *.c10 file specified by OUTPUT_FILE.
Options:
--version Show the version and exit.
--help Show this message and exit.
Developing and Testing
You will need a fairly modern python environment with uv installed.
You can begin by entering:
make install-pre-commit
make sync
make run-tests
The Makefile makes it easy to perform the most common operations:
make check-allruns linting, type checks, anduv.lockchecksmake check-lintchecks for linting issuesmake check-lockverifies theuv.lockis aligned topyproject.tomlmake check-typesruns thetytype checkermake cleancleans the virtual environment and cachesmake defaultruns a default set of checks on the codemake fix-allformats the code, fixes lint errors and runs locksuv.locktopyproject.tomlmake fix-formatformats the codemake fix-lintfixes linting issuesmake fix-lint-unsafefixes linting issues potentially adding inadvertant bugsmake helpoutputs the different make optionsmake installbuild install the distributionmake install-pre-commitinstalls pre-commit hooksmake locklocksuv.locktopyproject.tomlmake run-testsruns the unit testsmake syncsyncs the python environment withuv.lock
.vscode/settings.json is set so that unit tests can be run without further configuration.
Release files for mc10-tools 0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mc10_tools-0.11.tar.gz | 11.3 kB | Details |
Release files / mc10_tools-0.11.tar.gz
| Download URL | mc10_tools-0.11.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68abc41916fe6df0a00685f63b4cdbacfcdd443f112bc960192edf4959e3c498
|
|
BLAKE2b-256 checksum How to use checksums |
54b69c170d46075e9944d4ae507bc33ce75a05194230464affd7293a5d4dbd64
|
| 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 7, 2026.
Transparency log