mmpycorex
This package contains modules for downloading and installing MM through python, and for accessing the Java core of a running micro-manager instance, creating a headless java core object for access through python, or creating and instance of the python wrapper of the core (pymmcore)
Installation
pip install mmpycorex
Programatically installing Micro-Manager
- Python utility functions for downloading and installing Micro-Manager
from mmpycorex import download_and_install_mm, find_existing_mm_install
# this automatically installs the latest nightly build
# specify destination="your/custom/path", otherwise it will default to 'C:/Program files/Micro-Manager/'
# on windows or the home directory on mac
installed_path = download_and_install_mm()
Accessing the Java core through python
### Java Core example
from mmpycorex import create_core_instance, terminate_core_instances, get_default_install_location
# If micro-manager is alread running, you can get access to the core directly
# (just make sure the "run server" in the tools options dialog is checked)
# Otherwise you must create an instance of the Core in headless mode
mm_location = get_default_install_location() # 'C:/Program files/Micro-Manager/'
config_file = 'MMConfig_demo.cfg'
create_core_instance(mm_location, config_file, python_backend=False) # Create a remote MMCoreJ object
# Now that a core is running (either through the MM App or headless mode), create an object to access it
core = Core()
#### use the core
terminate_core_instances()
Accessing the python core (pymmcore)
### pymmcore example
from mmpycorex import create_core_instance, terminate_core_instances
# Otherwise you must create an instance of the Core in headless mode
mm_location = get_default_install_location() # 'C:/Program files/Micro-Manager/'
config_file = 'MMConfig_demo.cfg'
create_core_instance(mm_location, config_file, python_backend=True) # Create pymmcore instance
# Now that a core is running (either through the MM App or headless mode), create an object to access it
core = Core()
#### use the core
terminate_core_instances()
Install issues on M1 Macs
https://github.com/conda-forge/miniforge/issues/165#issuecomment-860233092
Metadata
Release files for mmpycorex 0.3.16
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 |
|---|---|---|---|---|
| mmpycorex-0.3.16.tar.gz | 168.1 kB | With provenance | Details for mmpycorex-0.3.16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mmpycorex-0.3.16-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for mmpycorex-0.3.16-py2.py3-none-any.whl |
Total release size: 178.9 kB
Release files / mmpycorex-0.3.16.tar.gz
| Download URL | mmpycorex-0.3.16.tar.gz |
|---|---|
| Size | 168.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d29d7e0b6cdff8c798a972b76c6d646e2fdbc45c9645b0ffdadcfb6be8b10cd1
|
|
BLAKE2b-256 checksum How to use checksums |
9ffce68e75e6df43abd12e5ab4c143dbf2cfd0374b7cd2be801618994fe7545f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 1, 2025.
Transparency logRelease files / mmpycorex-0.3.16-py2.py3-none-any.whl
| Download URL | mmpycorex-0.3.16-py2.py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b6b2856200c7774052b48175110b4a23cc53620d53c1254df6c9b5cf47bafa49
|
|
BLAKE2b-256 checksum How to use checksums |
d511f2219a36e14c0821ad239b976228e8f53bb7718d03ec9aeb3102a5cdaa8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 1, 2025.
Transparency logSecurity for mmpycorex 0.3.16
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mmpycorex-0.3.16.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 Apr 1, 2025.
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.