Subset of Modelica Standard Library that is required in rtc-tools and parsable by pymoca>=0.10.0 (which no longer declares Modelica as a builtin type, see https://github.com/pymoca/pymoca/commit/cf6d6a3b259983afe6e9d43c079da33901f17e34).
Modelica/Icons.mo is vendored alongside Modelica/Units.mo and
Modelica/SIunits.mo because both extend several Modelica.Icons.* classes
that pymoca no longer resolves on its own.
Included files
| File | MSL version | Namespace |
|---|---|---|
Modelica/Units.mo |
4.0.0 | Modelica.Units.* |
Modelica/SIunits.mo |
3.2.3 | Modelica.SIunits.* (deprecated, kept for backwards-compatibility with models that have not yet migrated) |
Modelica/Icons.mo |
4.0.0 | Modelica.Icons.* (vendored dependency of Units.mo and SIunits.mo) |
Metadata
Release files for rtc-tools-standard-library 0.1.3
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 |
|---|---|---|---|---|
| rtc_tools_standard_library-0.1.3.tar.gz | 41.2 kB | With provenance | Details for rtc_tools_standard_library-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rtc_tools_standard_library-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for rtc_tools_standard_library-0.1.3-py3-none-any.whl |
Total release size: 83.7 kB
Release files / rtc_tools_standard_library-0.1.3.tar.gz
| Download URL | rtc_tools_standard_library-0.1.3.tar.gz |
|---|---|
| Size | 41.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b64bf7f378618ed73b42769fc3f099cdb62d47ca1b379ec6eaee86537421bda4
|
|
BLAKE2b-256 checksum How to use checksums |
ee222fd5cc889a0499dc49f2b84a8392498096f25067a55173b2fff28c630fca
|
| 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 24, 2026.
Transparency logRelease files / rtc_tools_standard_library-0.1.3-py3-none-any.whl
| Download URL | rtc_tools_standard_library-0.1.3-py3-none-any.whl |
|---|---|
| Size | 42.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6a7230c3e701f3cf0e0e97560df5a3e0329814847227c865b5db4064a88e1f3
|
|
BLAKE2b-256 checksum How to use checksums |
1f7b3a714919b939d905c7e2144ed125140493946b3db1eb492826e0972b98db
|
| 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 24, 2026.
Transparency logSecurity for rtc-tools-standard-library 0.1.3
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for rtc_tools_standard_library-0.1.3.tar.gz
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 24, 2026.
Transparency logA 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.