mgcomm
Usually when writing some CLI apps I end up writing the same stuff over and over again. Like searching for configuration files according to Freedesktop’s standards. Or handling user input from either which can be collected from stdin, read from a file or piped in. This kind of stuff. So I decided to collect it in a small (probably personal) library which actually has some tests, sane interface and most important: can be easily used just by adding it to requirements.txt.
1 maintainer
Metadata
1 maintainer
Release files for mgcomm 0.2.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 | Actions |
|---|---|---|---|---|
| mgcomm-0.2.0.tar.gz | 5.2 kB | Without provenance | Details for mgcomm-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mgcomm-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for mgcomm-0.2.0-py3-none-any.whl |
Total release size: 10.1 kB
Release files / mgcomm-0.2.0.tar.gz
| Download URL | mgcomm-0.2.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b30704caf12fb78d8a4671be840b92509f6657b84500123b708b46177460ee00
|
|
BLAKE2b-256 checksum How to use checksums |
f71cdb8d22bd4a793c25361cf4fbcc33b22912b520b8a11f432de5df2731a36d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / mgcomm-0.2.0-py3-none-any.whl
| Download URL | mgcomm-0.2.0-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a0c306585e7c019a4c04586637a68b3629d5eef46397fa16d10520c3e3b5987
|
|
BLAKE2b-256 checksum How to use checksums |
aab8126e7f462362f23b277d8c78a65980eb152babb5c44b9b9addca38bc07c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mgcomm 0.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
