Micc2_ is a Python project manager: it helps you organize your Python project from simple single file modules to fully fledged Python packages containing modules, sub-modules, apps and binary extension modules written in Fortran or C++. Micc2 organizes your project in a way that is considered good practice by a large part of the Python community.
Micc2 helps you create new projects. You can start small with a simple one-file package and add material as you go, such as:
Python sub-modules and sub-packages,
applications, also known as command line interfaces (CLIs).
binary extension modules written in C++ and Fortran. Boiler plate code is automatically added as to build these binary extension with having to go through al the details. This is, in fact, the foremost reason that got me started on this project: For High Performance Python it is essential to rewrite slow and time consuming parts of a Python script or module in a language that is made for High Performance Computing. As figuring out how that can be done, requires quite some effort, Micc2 was made to automate this part while maintaining the flexibility.
Micc2 adds typically files containing example code that shows you how to add your own functionality.
You can automatically extract documentation from the doc-strings of your files, and build html documentation that you can consult in your browser, or a .pdf documentation file.
With a little extra effort the generated html documentation is automatically published to readthedocs.
Micc2 helps you with version management and control.
Micc2 helps you with testing your code.
Micc2 helps you with publishing your code to e.g. PyPI, so that you colleagues can use your code by simply running:
> pip install your_nifty_package
Credits
Micc2 does not do all of this by itself. For many things it relies on other strong open source tools. Here is a list of tools micc2 is using or cooperating with happily:
Pyenv: management of different Python versions on your desktop.
Poetry for packaging and publishing.
Git for version control.
Pytest for testing your code.
Sphinx to extract documentation from your project’s doc-strings.
CMake is used for building binary extension modules written in C++ and Fortran.
F2py for transforming modern Fortran code into performant binary extension modules interfacing nicely with numpy arrays.
Pybind11 as the glue between C++ source code and performant binary extension modules, also interfacing nicely with numpy arrays.
Roadmap
These features are still on our wish list:
1 maintainer
Metadata
1 maintainer
Release files for et-micc2 4.0.0
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 | |
|---|---|---|---|---|
| et_micc2-4.0.0.tar.gz | 82.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| et_micc2-4.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 188.5 kB
Release files / et_micc2-4.0.0.tar.gz
| Download URL | et_micc2-4.0.0.tar.gz |
|---|---|
| Size | 82.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c16b480293841ef66f50a6f69ab7d3a39db855e5ff75ea493fe5f41b74e8802a
|
|
BLAKE2b-256 checksum How to use checksums |
171f532bf05e51e5e092051ea210a1a82ac0130677a43c7b067e15d732dc27fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.8.5 Darwin/22.5.0
|
Release files / et_micc2-4.0.0-py3-none-any.whl
| Download URL | et_micc2-4.0.0-py3-none-any.whl |
|---|---|
| Size | 106.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
83ab448d7770d1f4780e9749a1d96e592c55eb37a5f670fac32683549600a148
|
|
BLAKE2b-256 checksum How to use checksums |
984712491a95df40c5733b1374fb21c5a61c1c3320baf6a138c7effc35f3566f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.8.5 Darwin/22.5.0
|
Security for et-micc2 4.0.0
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.
