Flask-events

Latest version: v0.7.0

Safety actively analyzes 706267 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

0.7.0

Changed
- Final release with compatibility for newer flask versions. Also marks the project inactive, use OTel for new projects.

0.6.0

Changed
- License changed from MIT to Hippocratic.

Added
- `events.instrument()` added as a decorator you can use to instrument a single function call.
- Official support for python 3.8.

0.5.1

Changed
- Before 0.5.0 flask-events would silently ignore being used outside the app context. With 0.5.0
that changed to a hard failure, which makes some use cases more convulated without much benefit.
The pre-0.5.0 behavior has been restored, with a logged warning that it's being used outside of
an app context.

0.5.0

Removed
- Support for python 3.4.

Added
- You can turn on opt-in anonymization of IPs in the default context by setting
`EVENTS_ANONYMIZE_IPS` to `True` (default settings), or a dict with the keys `ipv4_mask` and
`ipv6_mask` to customize the masks used.

0.4.0

Added
- celery tasks can now be instrumented too! Use `.init_celery_app` instead of `.init_app` to
automatically instrument all celery tasks.

0.3.0

Fixed
- The logfmt outlet now formats 0 correctly (previously it would be empty string),0 and outputs
True/False in lowercase, and by default formats floats with four digits.

Added
- If running on Heroku and the `runtime-dyno-metadata` labs feature is enabled the release version
and slug commit will be included by default.
- Added `handler` by default which is the qualified path to the function that handled the request.

Page 1 of 2

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.