OakEmu-Python
Python wrappers for the OakEmu project.
Local development
Use Python 3.13–3.15, uv and the .NET 10 runtime.
uv sync --locked
uv run coverage run --branch --source=src --m pytest --junitxml=test-results.xml
uv run ruff check
uv run ruff format --check
uv run ty check
Preview documentation
With uv and Docker installed, run python3 docs/preview.py, or select Preview documentation in a JetBrains IDE.
Open http://localhost:5173/OakEmu-Python/. Restart the preview after editing source or documentation.
The API is generated statically from Python source; previewing it does not load .NET. Generated output under artifacts/ is ignored.
Releases
Build and Test validates Python 3.13, 3.14 and 3.15, with documentation validated on Python 3.14.
Release builds and tests before publishing packages and documentation. Either publication can be disabled;
turn packages off to update documentation without uploading another PyPI version. No release tag is created for a docs-only run.
A blank release version increments the latest stable Git tag's minor version, starting from 0.0.0 before the first tagged release.
For the first docs-only deployment after this port, set api-ref to main: the historical v0.0.45 source predates
the corrected public exports and API docstrings. After the next package release, leave it blank.
The package version is derived from Git tags using hatch-vcs; there is no fixed version to update in pyproject.toml.
Local builds between releases receive a development version. Release builds use the workflow-selected version.
Configure GitHub Pages to use GitHub Actions. For package publication, configure a PyPI Trusted Publisher for this repository,
workflow release.yml and environment github-pages; no long-lived PYPI_API_KEY is used.
1 maintainer
Metadata
1 maintainer
Release files for mrkwatkins-oakemu 0.0.46
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 | |
|---|---|---|---|---|
| mrkwatkins_oakemu-0.0.46.tar.gz | 694.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mrkwatkins_oakemu-0.0.46-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / mrkwatkins_oakemu-0.0.46.tar.gz
| Download URL | mrkwatkins_oakemu-0.0.46.tar.gz |
|---|---|
| Size | 694.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a38be0c1234c189a4d9c94cb866ffcd5b95cfc4544dd4bc7a46c7970cb395e9
|
|
BLAKE2b-256 checksum How to use checksums |
dfb357c4449f3c98d2220a8993a36aa83ec9ced4eef31bed0045a884564ec8e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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 / mrkwatkins_oakemu-0.0.46-py3-none-any.whl
| Download URL | mrkwatkins_oakemu-0.0.46-py3-none-any.whl |
|---|---|
| Size | 705.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9a516eed51aeef117a1dd9ae1b7322b5b9c71ac6e5b0d9fed35b0e2322eabad
|
|
BLAKE2b-256 checksum How to use checksums |
b3a00a994193b125acc6f966c9f746dc5c734fba8416d7f9f258a983fefcdc21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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 mrkwatkins-oakemu 0.0.46
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.
