Motivation
The Italian participation at the 2010 South African world cup whose a complete disaster and watching our beloved team was a nightmare.
While watching our last at the office, in order to survive to this shame, I started a BDD package that would inject a vuvuzela on a Plone site.
In order to share my pain I then decided to publish this package.
Installation
Add to your buildout the following code:
[instance] ... eggs = ... rt.vuvuzela ... # Not required for Plone >= 3.3 zcml = ... rt.vuvuzela ...
Todo
- Add:
a portlet
a viewlet
How to use it
Come on man! Are you sure?
Ok, if you are brave enough just add @@vuvuzela to the url of your Plone site, pointing to a url like this http://localhost:8080/Plone/@@vuvuzela
Forgive me, please :)
BDD: Beer Driven Development
Metadata
Release files for rt.vuvuzela 1.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 |
|---|---|---|---|---|
| rt.vuvuzela-1.0.1.tar.gz | 15.0 kB | Without provenance | Details for rt.vuvuzela-1.0.1.tar.gz |
Release files / rt.vuvuzela-1.0.1.tar.gz
| Download URL | rt.vuvuzela-1.0.1.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5e6dad350433c9a56cb5904bf13242f897e7c0f51280a9370c54fae4ccfd1eb
|
|
BLAKE2b-256 checksum How to use checksums |
ecff22c50f88f805131dcd7441cc40933bb9ac5916c4a1fffb7d3911c5c53da9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rt.vuvuzela 1.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.