pyramid_retry
pyramid_retry is an execution policy for Pyramid that wraps requests and can retry them a configurable number of times under certain “retryable” error conditions before indicating a failure to the client.
See https://docs.pylonsproject.org/projects/pyramid-retry/en/latest/ or docs/index.rst in this distribution for detailed documentation.
2.1.1 (2020-03-21)
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 (2019-09-30)
Add exception and response attributes to the pyramid_retry.IBeforeRetry event. See https://github.com/Pylons/pyramid_retry/pull/19
2.0 (2019-06-06)
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 (2018-10-18)
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 (2017-06-19)
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 (2017-06-12)
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
0.3 (2017-04-10)
Support a retry.activate_hook setting which can return a per-request number of retries. See https://github.com/Pylons/pyramid_retry/pull/4
Configuration is deferred so that settings may be changed after config.include('pyramid_retry') is invoked until the configurator is committed. See https://github.com/Pylons/pyramid_retry/pull/4
Rename the view predicates to last_retry_attempt and retryable_error. See https://github.com/Pylons/pyramid_retry/pull/3
Rename pyramid_retry.is_exc_retryable to pyramid_retry.is_error_retryable. See https://github.com/Pylons/pyramid_retry/pull/3
0.2 (2017-03-02)
Change the default attempts to 3 instead of 1.
Rename the view predicates to is_last_attempt and is_exc_retryable.
Drop support for the tm.attempts setting.
The retry.attempts setting is always set now in registry.settings['retry.attempts'] so that apps can inspect it.
0.1 (2017-03-01)
Initial release.
Release files for pyramid-retry 2.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 | Actions |
|---|---|---|---|---|
| pyramid_retry-2.1.1.tar.gz | 23.3 kB | Without provenance | Details for pyramid_retry-2.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyramid_retry-2.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for pyramid_retry-2.1.1-py2.py3-none-any.whl |
Total release size: 29.9 kB
Release files / pyramid_retry-2.1.1.tar.gz
| Download URL | pyramid_retry-2.1.1.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
baa8276ae68babad09e5f2f94efc4f7421f3b8fb526151df522052f8cd3ec0c9
|
|
BLAKE2b-256 checksum How to use checksums |
bf022a084e7bc8ca3c50b67c6a6d58598c5771d93399e9ff2aadf6aa29c1adcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/46.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.4
|
Release files / pyramid_retry-2.1.1-py2.py3-none-any.whl
| Download URL | pyramid_retry-2.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b5129a60eb9d7409234ea52839006426d2ae887b4a1f0530c75ec336cabf2476
|
|
BLAKE2b-256 checksum How to use checksums |
b7a7b04390f36dcd0b117e023e4f980d6173da893b3c27f8b12ecd5dcc6fdb95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/46.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.4
|
Security for pyramid-retry 2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
