buildout.autoextras
Buildout (zc.buildout) extension for including setuptools extras_require options for all items in a target option if the extra exists.
Usage
This is a buildout extension, so simply add it to your extensions list:
[buildout] extensions = buildout.autoextras
Options
There are two options…
- autoextra-keys
A list of extra keys (e.g. test, zcml, etc.) that should be included if the package has the extra.
- autoextra-targets
A list of targets to check for the extras. For example, a buildout part named demo that has an eggs option. The target in this case would be demo:eggs. This is similar to zc.buildout’s variable replace syntax except without the ${} symbolling.
Together these options might look something like:
[buildout]
extensions = buildout.autoextras
parts = demo
autoextra-keys = zcml
autoextra-targets = demo:eggs
[demo]
recipe = zc.recipe.eggs
eggs =
zope.testing
zope.i18n
Changelog
1.1 (2011-10-25)
Monkeypatching zc.buildout.easy_install.Installer’s install method in order to post-process the distributions. Otherwise, we run into an order of operations problem (e.g. obtaining eggs before some eggs have been marked for development). [pumazi]
1.0 (2011-10-21)
Initial release. [pumazi]
Metadata
Release files for buildout.autoextras 1.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.autoextras-1.1.tar.gz | 6.2 kB | Without provenance | Details for buildout.autoextras-1.1.tar.gz |
Release files / buildout.autoextras-1.1.tar.gz
| Download URL | buildout.autoextras-1.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c88d2025621c458bffa8b6b7e6bf22f6ec28ee0ee3412047da23f8a84e8ffc34
|
|
BLAKE2b-256 checksum How to use checksums |
61938426b1010ae25dac839fcacf1ebb873223ce3564439cc89921056dfa35cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for buildout.autoextras 1.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.