Pyramid-retry

Latest version: v2.1.1

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

Scan your dependencies

Page 1 of 2

2.1.1

==================

- Ensure the threadlocals are properly popped if the ``activate_hook`` throws
an error or the request body fails to read due to a client disconnect.
See https://github.com/Pylons/pyramid_retry/pull/20

2.1

================

- Add ``exception`` and ``response`` attributes to the
``pyramid_retry.IBeforeRetry`` event.
See https://github.com/Pylons/pyramid_retry/pull/19

2.0

================

- No longer call ``invoke_exception_view`` if the policy catches an exception.
If on the last attempt or non-retryable then the exception will now bubble
out of the app and into WSGI middleware.
See https://github.com/Pylons/pyramid_retry/pull/17

1.0

================

- Support Python 3.7.

- Update the version we require for Pyramid to a non-prerelease so that pip and
other tools don't accidentally install pre-release software.
See https://github.com/Pylons/pyramid_retry/pull/13

0.5

================

- Update the policy to to track changes in Pyramid 1.9b1. This is an
incompatible change and requires at least Pyramid 1.9b1.
See https://github.com/Pylons/pyramid_retry/pull/11

0.4

================

- Add the ``mark_error_retryable`` function in order to easily mark
certain errors as retryable for ``pyramid_retry`` to detect.
See https://github.com/Pylons/pyramid_retry/pull/8

- Add the ``IBeforeRetry`` event that can be subscribed to be notified
when a retry is about to occur in order to perform cleanup on the
``environ``. See https://github.com/Pylons/pyramid_retry/pull/9

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.