fry
All right! I'm a delivery boy!
Description
Fry is an extension of the python requests library built to better manage service-level http interactions.
- Manages dependency settings within the Session object, lessening the amount of overhead boilerplate code
- Dependency settings include retry count and timeout; split per host
- Given a statsd object, will also record and report stats per request; split per endpoint
StatsD libraries currently supported:
- datadog
Usage
import fry
adapter_settings = {
'http://www.example.com': {
'retry': {
'total': 3,
'read': 3
},
'adapter': {
'pool_maxsize': 4,
},
'adapter_config': {
'timeout': 0.5
}
}
}
fsession = fry.FrySession(stats_client=DogStatsd('example'), adapter_settings=adapter_settings)
signature = 'hostname.endpoint'
request_params = {'test': 'value'}
response = fsession.make_request('GET', 'http://www.example.com', signature, params=request_params)
Development
Update the version when updating the library in: fry/__init__.py
Build the library locally: python setup.py sdist
Change Log
0.2.0
- Support for datadog statsd api
Metadata
Release files for fry 0.2.0
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 |
|---|---|---|---|---|
| fry-0.2.0.tar.gz | 4.7 kB | Without provenance | Details for fry-0.2.0.tar.gz |
Release files / fry-0.2.0.tar.gz
| Download URL | fry-0.2.0.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76ee45d30a444151cf72193b7dcde03cbf0255a6be3db179c08b462d96661fb3
|
|
BLAKE2b-256 checksum How to use checksums |
8234e68a4a6b6ff16cef2b5b298ba5df165b08727a084e27cfd6680194fb92e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.37.0 CPython/3.7.4
|
Security for fry 0.2.0
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.