1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
plone.recipe.distros
Options
- urls
The URLs of the archives to download. The archives specified in the same part will be extracted into the same parts folder named after the part. The full path to that folder will be available as ‘location’ from the parts option dictionary.
- nested-packages
The file names of one or more of the archives in the urls list. This will cause only the Python packages (identified by a __init__.py) in the top folder in the archive to be extracted into the destination.
- version-suffix-packages
The file names of one or more of the archives in the urls list. This will cause the part after the last dash to be omitted from the created destination folder.
Reporting bugs or asking questions
We have a shared bugtracker and help desk on Launchpad: https://bugs.launchpad.net/collective.buildout/
Changelog
1.5 (2009-06-23)
Create download-cache directory when not provided by buildout [gotcha, jfroche]
Simplified package metadata. [hannosch]
1.4 (2009-04-04)
Added support for urls with http authentication. [mond21]
1.3
Allow download-cache to fallback to download-directory if present. [smcmahon]
1.2
Renamed download-directory to download-cache, which is the name that is used by zc.buildout itself. [hannosch]
1.1
Document the options, added README and CHANGES. [hannosch]
1.0
First final release. Cleaned up setup.py. [hannosch]
0.3
Handle nested packages where the packages are the top level folders as well. This is needed for the PloneLDAP and ScriptableFields bundles. [wichert]
Better error handling. This prevents buildout from reporting an internal error and informs the user what failed to download and why. [wichert]
0.2
Make sure the directory exists even if the first package is a version suffix or nested one :) [optilude]
0.1
Initial implementation. [hannosch]
Release files for plone.recipe.distros 1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| plone.recipe.distros-1.5.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| plone.recipe.distros-1.5-py2.4.egg | Legacy Egg format | - | - | Details |
Total release size: 12.1 kB
Release files / plone.recipe.distros-1.5.tar.gz
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | plone.recipe.distros-1.5.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
befd78bed38a8a0516da303014b351d0a08674317f67ec69b06aa27e7327bf66
|
|
BLAKE2b-256 checksum How to use checksums |
450b9c05011e08b40de9bf3e1e64ba2d0b11c5dad1872d7462cdbad20b516c26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / plone.recipe.distros-1.5-py2.4.egg
| Download URL | plone.recipe.distros-1.5-py2.4.egg |
|---|---|
| Size | 7.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
22687043ecbea91275f7d83e28bda1365b64eee553727b667552125b00045c99
|
|
BLAKE2b-256 checksum How to use checksums |
f2d20793f3ac54952880508fe7877cd9e95a4dd917851c262264c94c50767514
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.recipe.distros 1.5
Upload timing
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.
