Introduction
buildout.extensionscripts is a convenient way to shoot yourself in the foot and provides more than enough rope to hang yourself.
With that out of the way, we can look what it can be used for.
To use buildout.extensionscripts, you add it as an extension in a buildout like this:
[buildout] extensions = buildout.extensionscripts
After that you can add one or more lines like the following to the buildout section:
extension-scripts =
${buildout:directory}/somescript.py:callable_name
When you do that, you got an easy way to write a buildout extensions without the need of an egg. The callable_name in somescript.py will be called with one argument which is the dictionary like buildout config.
Now have fun shooting and or hanging yourself by changing that.
Changes
1.1 - 2025-04-26
Support Python 3.12.
1.0 - 2009-10-07
Initial release.
Metadata
Release files for buildout.extensionscripts 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 | |
|---|---|---|---|---|
| buildout_extensionscripts-1.1.zip | 6.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| buildout_extensionscripts-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / buildout_extensionscripts-1.1.zip
| Download URL | buildout_extensionscripts-1.1.zip |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0aff96cb1902d86bbad01eb1529460d028a1aa2912f4f8438cd79bd167454297
|
|
BLAKE2b-256 checksum How to use checksums |
687a68796c3f3962d3ae2225b3a2db00d45e59472f1d0494de9135f1f7dab4e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
devpi-server/6.14.0 (py3.11.11; darwin)
|
Release files / buildout_extensionscripts-1.1-py3-none-any.whl
| Download URL | buildout_extensionscripts-1.1-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
359023a58e3ce2dfb6524c29de592f6357bb11ee61128c86a0e3f7019c065f70
|
|
BLAKE2b-256 checksum How to use checksums |
f79bb3aaffdd5c867aa60481673a05918b041f96b330867eb37a5246af0633a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
devpi-server/6.14.0 (py3.11.11; darwin)
|
Security for buildout.extensionscripts 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.