- Web:
- Git:
git clone git://github.com/peritus/buildout-md5sums.git (browse source)
- Download:
Simple usage
Use a buildout.cfg like this and the md5sum for the download-python target will be checked:
[buildout]
extensions = buildout-md5sums
md5sums =
http://python.org/ftp/python/2.6.6/Python-2.6.6.tar.bz2 = 376df294ae16e9601da989f8c4d8d432
http://python.org/ftp/python/2.7/Python-2.7.tar.bz2 = 0e8c9ec32abf5b732bea7d91b38c3339
parts = download-python
[versions]
python = 2.6.6
[download-python]
recipe = hexagonit.recipe.download
url = http://python.org/ftp/python/${versions:python}/Python-${versions:python}.tar.bz2
Using this setup, you can switch the downloaded version of python on the command line while keeping the cryptographic checking alive:
$ ./bin/buildout versions:python=2.7 install download-python
Disallowing downloads without md5sums
If your buildout.cfg like this, the extension will make the buildout fail if there is a download using zc.buildout.download without a md5sum specified:
[buildout] extensions = buildout-md5sums allow-picked-downloads = false
1 maintainer
Metadata
1 maintainer
Release files for buildout-md5sums 0.1
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 |
|---|---|---|---|---|
| buildout-md5sums-0.1.tar.gz | 4.0 kB | Without provenance | Details for buildout-md5sums-0.1.tar.gz |
Release files / buildout-md5sums-0.1.tar.gz
| Download URL | buildout-md5sums-0.1.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9cf9f8ee90c7efb2f3c552e4616427db313a61fa5f08cfead5bf305f501f9c9
|
|
BLAKE2b-256 checksum How to use checksums |
c133270dfef28e480bfae0cf1bbd2a8afd7d45faab2044dcb4afd1c5cbaabcb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for buildout-md5sums 0.1
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.
