From the Jargon File:
The -P Convention Turning a word into a question by appending the syllable ‘P’; from the LISP convention of appending the letter ‘P’ to denote a predicate (a boolean-valued function). The question should expect a yes/no answer, though it needn't. (See T and NIL.)
retryp is yet another retry decorator, with nothing particularly special about it other than it being both well-featured and not rewriting or hiding the calling signature of the wrapped method (allows for accurate code introspection – a Big Deal for me).
Thanks go to Graham Dumpleton and his wrapt package for that latter.
Arguments
- count
Default: 10
Number of times to retry the wapped item. If set to “0”, will retry 1073741823 times because a) that’s a lot, b) give up already, and c) nothing lasts forever.
- delay
Default: 10 (seconds)
The base delay between retry attempts.
- backoff
Default: 10
A multiplicative factor applied to the delay, used to provide increasing backoff as subsequent attempts continue to fail.
- jitter
Default 0
Extra random seconds will be added to each retry delay, ranging from 0 to the value of jitter.
- refuse_rc_fn
Default: None
If provided, the return of the wrapped item will be passed as the only argument to this function. If refuse_rc_fn (rc) evaluates to True, then no further retries will be made.
- refuse_exc_fn
Default: None
If provided, any exception raised by the wrapped item will be passed as the only argument to this function. If refuse_exc_fn (e) evaluates to True, then the exception will be raised again and retry attempts will cease.
- expose_last_exc
Default: False
By default retryp will raise retryp.FailedTooOften if the wrapped item continues to fail after the requested number of attempts. If expose_last_exc is set, then the exception raised by the wrapped item will be raised if the last attempt results in an exception.
- log_faults
Default: False
Log every exception raised by the wrapped item using logtool.log_fault.
- log_faults_level
Default: logging.DEBUG
Logging level at which exceptions will be logged by logtool.log_fault() when log_faults is set.
1 maintainer
Metadata
1 maintainer
Release files for retryp 0.1.post20
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 | |
|---|---|---|---|---|
| retryp-0.1.post20.tar.gz | 23.4 kB | Without provenance | Details |
Release files / retryp-0.1.post20.tar.gz
| Download URL | retryp-0.1.post20.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5d8b9904b5912d45288de71feca97028906df27b97e975aae5d14a6e313df96
|
|
BLAKE2b-256 checksum How to use checksums |
c4aa46116076b6a16e4d81cb930cfeb1da78ea6321faf9abad92a42ab98f978b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for retryp 0.1.post20
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.
