Installation
pip install async-fetcher
# or
pip install -e git+https://github.com/night-crawler/async-fetcher.git@#egg=async-fetcher
Sample
af = AsyncFetch({
'first': AsyncFetch.mk_task(build_url('request-info')),
'second': AsyncFetch.mk_task('http://example.com/'),
'fail': AsyncFetch.mk_task(build_url('404'))
})
responses = af.go()
mk_task static method can take this arguments:
:param fail_silently: bool, do not raise exceptions, default is False;
for test purpose, do not use in production
:param num_retries: int, *optional*, default is -1; -1 - no retries; 0 - use AsyncFetch.num_retries
:param autodetect_content_type: if no `content-type` header was specified, set `content-type` as
`application/json` for dict, and `text/html` otherwise; default is True
:param json_encoder: JSONEncoder, *optional*, JSON encoder for data serialization
tries to use DRF's encoder, or default JSONEncoder from json package; default is JSONEncoder
:param url: str, *required*, url address
:param api_key: str, optional API key passed into HEADERS dict
:param data: dict, *optional*, request data. Default is None,
:param method: str, *optional*, HTTP request method. Default is True.
:param headers: dict, *optional*, optional HTTP headers
:param response_type: str, *optional*, HTTP response type
(in fact it's just aiohttp's method name, i.e. text, or json); default is 'json'
:param language_code: str, set `accept-language` header
:param timeout: float, *optional*, time to wait for response in seconds before TimeoutError
:param query: dict, *optional*, url get arguments
:param do_not_wait: bool, *optional*, fail silently with no retries and empty resultset
af0 = AsyncFetch({})
tcp_connector = af0.get_tcp_connector()
af1 = AsyncFetch({
'1': AsyncFetch.mk_task(build_url('request-info')),
'2': AsyncFetch.mk_task(build_url('request-info')),
}, tcp_connector=tcp_connector)
responses = af1.go()
Metadata
Release files for async-fetcher 0.3.6
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 |
|---|---|---|---|---|
| async-fetcher-0.3.6.tar.gz | 9.1 kB | Without provenance | Details for async-fetcher-0.3.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| async_fetcher-0.3.6-py3-none-any.whl | Python 3 | none | any | Details for async_fetcher-0.3.6-py3-none-any.whl |
Total release size: 21.1 kB
Release files / async-fetcher-0.3.6.tar.gz
| Download URL | async-fetcher-0.3.6.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
054717b2158494e121f04f525d26d9d6ce48161a351bc725b6fed2279aa9c591
|
|
BLAKE2b-256 checksum How to use checksums |
de13c8fc375618da93acfc66616543f8113a434c4273d5038a0a94a884c3194d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Release files / async_fetcher-0.3.6-py3-none-any.whl
| Download URL | async_fetcher-0.3.6-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1e8ddf28a9215e36f9ae0e4e3c53747ef078fef426985c46fab5d9eb79b398f
|
|
BLAKE2b-256 checksum How to use checksums |
882b7d312a0d0385cbbeff7c61bee451be435f8d88b11f865111effa560fb20a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Security for async-fetcher 0.3.6
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.