mypythontools_cicd
Module with functionality around Continuous Integration and Continuous Delivery.
Why to use this and not Travis or Circle CI? It's local and it's fast. You can setup it as a task in IDE and if some phase fails, you know it soon and before pushing to repo.
You can also import mypythontools in your CI/CD and use it there of course.
If you are not sure whether the structure of your app will work with this code, check project-starter-cookiecutter on GitHub.
Links
Official documentation - readthedocs
Official repo - GitHub
Installation
Python >=3.6 (Python 2 is not supported).
Install with
pip install mypythontools_cicd
There are many extras requirements that can be used with square brackets like for example
pip install mypythontools_cicd[tests]
You can use dev which install libraries used during development like for example pylint. Most subpackages
has own extras. 'build_app','deploy', 'docs', 'git', 'misc', 'tests', 'venvs' in particular.
There is also cicd which install all libraries necessary for cicd, but without dev dependencies. Last
extras are all which use dev as well as cicd.
Subpackages
Package is divided into several subpackages
build_app
Build your application to .exe with pyinstaller. It also builds javascript frontend with npm build if configured, which is used mostly in PyVueEel applications.
cicd
Pipeline for all the other submodules, that provide configurable CI/CD.
deploy
Build package and push it to PyPi.
docs
Provide documentation with sphinx.
git
Works with git. You can check branch here, commit all changes or push to repository.
misc
Miscellaneous functions that are too small to have own subpackage, like for example formatting with black.
packages
For example, you can work with requirements here. Usually used in 'setup.py'.
project_paths
Subpackage where you can get paths used in your project (path to README, __init__.py etc.).
tests
Runs tests in more venvs with different python versions, also with wsl linux if configured and create coverage.
venvs
Works with virtual environments.
Mypythontools
There is extra library in separate repository which is not about CICD, but normal python helpers.
https://github.com/Malachov/mypythontools
This can help you with a lot of stuff around CICD like getting project paths, generating docs, testing, deploying to PyPi etc.
1 maintainer
Metadata
1 maintainer
Release files for mypythontools-cicd 0.0.35
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 | |
|---|---|---|---|---|
| mypythontools_cicd-0.0.35.tar.gz | 33.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mypythontools_cicd-0.0.35-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 74.8 kB
Release files / mypythontools_cicd-0.0.35.tar.gz
| Download URL | mypythontools_cicd-0.0.35.tar.gz |
|---|---|
| Size | 33.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46a192304fa9d11e1b33433b12a8ae3c9ecec00188d061d4453b1d672eb61291
|
|
BLAKE2b-256 checksum How to use checksums |
4dbcd268159b8d23dae5db940906c6c17b1aed9786d77f5f9ab8144902b0b6fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Release files / mypythontools_cicd-0.0.35-py3-none-any.whl
| Download URL | mypythontools_cicd-0.0.35-py3-none-any.whl |
|---|---|
| Size | 41.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
662306d82f3851c0bf77a11dc610e5e03b50a96c0da44c84032e552f3bbf7a87
|
|
BLAKE2b-256 checksum How to use checksums |
262fea868702a6a9928edf43caae3123b1b8666c93f4ff5fd934387989d31cf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Security for mypythontools-cicd 0.0.35
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.
