Skip to main content

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-all runs linting, type checks, and uv.lock checks
  • make check-lint checks for linting issues
  • make check-lock verifies the uv.lock is aligned to pyproject.toml
  • make check-types runs the ty type checker
  • make clean cleans the virtual environment and caches
  • make default runs a default set of checks on the code
  • make fix-all formats the code, fixes lint errors and runs locks uv.lock to pyproject.toml
  • make fix-format formats the code
  • make fix-lint fixes linting issues
  • make fix-lint-unsafe fixes linting issues potentially adding inadvertant bugs
  • make help outputs the different make options
  • make install build install the distribution
  • make install-pre-commit installs pre-commit hooks
  • make lock locks uv.lock to pyproject.toml
  • make run-tests runs the unit tests
  • make sync syncs the python environment with uv.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)

Source distribution for mc10-tools 0.11
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

Release history Release notifications | RSS feed

This release

0.11 This release

1 release file

0.10

1 release file

0.9

1 release file

0.8

1 release file

0.7

1 release file

0.6

1 release file

0.5

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page