This release is a pre-release and may not be stable for production use.
MIKE Core for Python
A project to facilitate use of the MIKE Core components with Python, targeting Windows as well as Linux.
The MIKE Core Python classes have an API which is almost identical to the MIKE Core .NET API, to the extend possible. Since Python does not support all the language constructions that .NET/C# does (as e.g. method overriding), the API's are not completely identical. Also, the number of classes in the Python version is also smaller, since Python classes can be formed while being used. However, the examples and documentation for the .NET/C# API is to a high degree applicable also for the use of MIKE Core Python. For details, visit:
This library is the foundation for MIKE IO.
Installation
pip install mikecore
Development
All commands are run from the project root.
-
Sync & Build
uv sync # Use 'uv sync --reinstall' to force-rebuild native components.
-
Update EUM Types (for new release, or whenever EUM.xml changes)
# Generate definitions from the new native build uv run ./buildUtil/eumXMLProcess.py > eumItemUnit.txt # Use a diff tool to merge changes into mikecore/eum.py.
-
Run Tests
uv run pytest
-
Build Packages (Optional)
uv build
Troubleshooting
Another library in the same process also loads MIKE Core
mikecore loads its bundled MIKE Core libraries by default, even with MIKE installed. With another library in the process that loads MIKE Core (a MIKE engine, for example):
- Linux: the two keep separate libraries, unless the other library is
loaded with
RTLD_GLOBALbefore mikecore. - Windows: each MIKE Core DLL is loaded once per process, by whichever library comes first, so the two can end up on a mix of versions.
To share one set instead, set MIKECORE_PYTHON_BIN to the installation's bin
folder (on Windows, the 64-bit bin\x64) before mikecore is first imported. On
Linux, you may also need that folder on LD_LIBRARY_PATH, and on Ubuntu 24.04
the installation's libraries may need sudo apt install libnsl2. mikecore is
only tested with its bundled libraries.
Either way, mikecore's EUM items and units match the bundled version. With
MIKE Core from a newer version, EUM lookups can raise ValueError
(#84), and data from it can
use items and units mikecore doesn't know. With an older version, newer items
and units are rejected.
Metadata
Release files for mikecore 0.3.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mikecore-0.3.0rc1-py3-none-any.whl | Python 3 | none | any | Details for mikecore-0.3.0rc1-py3-none-any.whl |
Release files / mikecore-0.3.0rc1-py3-none-any.whl
| Download URL | mikecore-0.3.0rc1-py3-none-any.whl |
|---|---|
| Size | 13.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a470bbe412da379045601ecd09bfa384ee489efd884fbe24adbeb6a5e0ed8b40
|
|
BLAKE2b-256 checksum How to use checksums |
7fd1659c19c1bfd4ccc2359fc13790bcbf9db9a125559be80691c3adaa354da1
|
| 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 Nov 12, 2026.
Transparency logSecurity for mikecore 0.3.0rc1
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
1 file in this release has been uploaded with provenance metadata.
Attestation for mikecore-0.3.0rc1-py3-none-any.whl
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 Nov 12, 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.