buildout.packagename is a zc.buildout extension which can be used to extract the package name of an adjacent setup.py to avoid redundancy. The extracted name is made available via the package-name variable in the [buildout] section, i.e. as ${buildout:package-name}.
Usage
An example buildout.cfg using the extension might look like this:
[buildout]
extensions = buildout.packagename
parts = app
[app]
recipe = zc.recipe.egg
interpreter = app
eggs = ${buildout:package-name}
Please note that since using this extension only makes sense for package-specific buildouts, the develop setting is set to “.” for added convenience.
Changelog
1.0 (2012-10-27)
Initial release. [witsch]
1 maintainer
Metadata
1 maintainer
Release files for buildout.packagename 1.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 |
|---|---|---|---|---|
| buildout.packagename-1.0.zip | 7.3 kB | Without provenance | Details for buildout.packagename-1.0.zip |
Release files / buildout.packagename-1.0.zip
| Download URL | buildout.packagename-1.0.zip |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ce504480fa13da810b13b87d75a1331482246136f518c2fe6d676694ba1ef91
|
|
BLAKE2b-256 checksum How to use checksums |
d9230476a07031dae53cf67fe8ef721fc6b026633c29efc58027a98713bd7363
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for buildout.packagename 1.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.
