mercurial-hug
This library provides a wrapper around select Mercurial functionality. We aim for the wrapper to be friendlier to use than Mercurial itself (the libraries, that is, which are largely undocumented) and also to provide a stable API. To achieve this, we will implement only the functionality we need, and if you ask nicely we might also implement the functionality you need too.
Also, Mercurial is licensed under the GPLv2+ and we use it under the terms of the GPLv3. This project is licensed according to the AGPLv3+, so if you’re looking for a cushion from the strict copyleft license, this library is not your answer.
Hosted on GitHub?!
I know it’s a little weird to host a project about Mercurial in a Git repository, but BitBucket is not impressive, and basically I didn’t think it was worth off-GitHub hosting just for this small library. Sorry!
Metadata
Release files for mercurial-hug 0.4.2
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 | |
|---|---|---|---|---|
| mercurial-hug-0.4.2.tar.gz | 5.8 kB | Without provenance | Details |
Release files / mercurial-hug-0.4.2.tar.gz
| Download URL | mercurial-hug-0.4.2.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e278aa4aee7e03fb6b4e798b6cd438070e180ddd20013205a52dc5c3dc97603b
|
|
BLAKE2b-256 checksum How to use checksums |
d472a503afec2df0e6a6079e46f6d61949f8eec73438548498b2fdc99e995111
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mercurial-hug 0.4.2
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.