urban.events
Events configuration for Urban
Features
Can be bullet points
Examples
This add-on can be seen in action at the following sites: - Is there a page on the internet where everybody can see the features?
Documentation
Full documentation for end users can be found in the “docs” folder, and is also available online at …
Translations
This product has been translated into
French
Installation
Install urban.events by adding it to your buildout:
[buildout]
...
eggs =
urban.events
and then running bin/buildout
Contribute
Issue Tracker: https://github.com/IMIO/urban.events/issues
Source Code: https://github.com/IMIO/urban.events
Support
If you are having issues, please let us know.
License
The project is licensed under the GPLv2.
Contributors
Martin Peeters [mpeeters] - Affinitic
Changelog
1.0.4 (2026-10-17)
New features:
Add the Prise de connaissance de la cession event config for unique and environmental (class 1 and 2) licences [WBoudabous] (URB-3636)
Add special conditions revision events (deposit, project, decision), tacit refusal, information, abandon and cession events [wboudabous] (URB-3669)
1.0.3 (2026-08-12)
New features:
Import event config for free notification [daggelpop] (URB-3561)
1.0.2 (2026-05-12)
New features:
Add events for EnvClassBordering and CODT_UniqueBorderingLicence [daggelpop] (URB-3470)
1.0.1 (2026-01-22)
Bug fixes:
Fix python requirement [mpeeters] (URB-3482)
1.0.0 (2026-01-22)
New features:
Add event config and upgrade step for roaddecree and housing [jchandelle] (URBBDC-3142)
1.0.0a5 (2024-06-27)
New features:
URB-3005: Add recepisse-de-plans-modificatifs to standard config [daggelpop] URB-3005: Move recepisse-de-plans-modificatifs config to appropriate package [daggelpop] (URB-3005)
1.0.0a4 (2024-03-23)
New features:
Update or fix TAL Condition on CODT 2024 new events. Fix eventType attribute on Urban classic. [mpeeters] (URB-3006)
1.0.0a3 (2024-03-18)
Bug fixes:
Fix an error with event config on Urban Classic [mpeeters] (URB-3006)
1.0.0a2 (2024-03-14)
Bug fixes:
Fix enum dependency [jchandelle] (URB-3006)
1.0.0a1 (2024-03-13)
New features:
Add function to import event config and create new CODT reform events at profile import. Split configuration files between urban classic and liege. [jchandelle, daggelpop, mpeeters] (URB-3006)
Bug fixes:
Avoid an error between liege and main urban branch Fix existing content handling [mpeeters, jchandelle] (URB-3006)
Metadata
Release files for urban.events 1.0.4
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 |
|---|---|---|---|---|
| urban_events-1.0.4.tar.gz | 2.7 MB | Without provenance | Details for urban_events-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| urban_events-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for urban_events-1.0.4-py3-none-any.whl |
Total release size: 5.4 MB
Release files / urban_events-1.0.4.tar.gz
| Download URL | urban_events-1.0.4.tar.gz |
|---|---|
| Size | 2.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd5760154207ca1da3fa14ef836ade94820fc7645201ac40c18e4bbe004e5599
|
|
BLAKE2b-256 checksum How to use checksums |
9ce90b001dd4edfb1b964371b6819d489559a820748443e7d73d2f83c86d030a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / urban_events-1.0.4-py3-none-any.whl
| Download URL | urban_events-1.0.4-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5dd1c3113c0e85a0190a0c5c7b4a5daf102755dfcf259c85094164e4f1560669
|
|
BLAKE2b-256 checksum How to use checksums |
13c0601b62ff82e2ac77b1abbf941e853e124b3b3536e5506e0afdf3dd74b409
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for urban.events 1.0.4
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.