This release is a pre-release and may not be stable for production use.
mosaik.Multi-Project
Tooling for setting up and maintaining multiple (mosaik) projects.
Motivation
mosaik scenarios often contain multiple simulators. Sometimes, additional packages need to be developed alongside of them. Managing such a set of loosely coupled projects becomes laborious easily. This project provides tooling for some common operations on projects. These operations range from cloning the repository to building a docker image. Operations can be run in parallel on projects, enabling quite some automation.
Status
The code of this project was largely in operation in the Designetz project.
One-line Execution
mosaik.Multi-Project can be run as a container directly from GitLab.com:
docker run registry.gitlab.com/offis.energy/mosaik/mosaik.multi-project:latest --help
Prerequisites
- Python 3.6+
- git
1 maintainer
Metadata
1 maintainer
Release files for mosaik.Multi-Project 0.1.0rc20210323234446
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 | Reset |
|---|---|---|---|---|
| mosaik.Multi_Project-0.1.0rc20210323234446-py3-none-any.whl | Python 3 | none | any | Details |
Release files / mosaik.Multi_Project-0.1.0rc20210323234446-py3-none-any.whl
| Download URL | mosaik.Multi_Project-0.1.0rc20210323234446-py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a2ac8b1c6220d9d4ea6b0dd70f9ec2105e1cdb2253d0f7d97315382ba47fa51
|
|
BLAKE2b-256 checksum How to use checksums |
aa6577f2b5c42de7ded8958355b538867c5790b04e5f2c997bff84b8bbfba3b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Security for mosaik.Multi-Project 0.1.0rc20210323234446
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.
