bezalel
A library for ingesting data provided by paginated HTTP APIs
Usage
Basic use case
If you have to pull data from HTTP API that has an endpoint accepting parameters:
pageNumber=1,2,...
And returning JSON:
{
"pageCount": 5,
"entities": [
{"key": "val1", ...},
{"key": "val2", ...},
...
]
}
Then you can iterate over all pages with following code:
import requests
from bezalel import PaginatedApiIterator
for page in PaginatedApiIterator(requests.Session(), url=f"http://localhost:5000/page-api",
request_page_number_param_name="pageNumber",
response_page_count_field_name="pageCount",
response_records_field_name="entities"):
print(f"Page: {page}")
It will print:
Page: [{"key": "val1", ...}, {"key": "val2", ...}, ...]
Page: [{"key": "val100", ...}, {"key": "val101", ...}, ...]
Page: [{"key": "val200", ...}, {"key": "val201", ...}, ...]
...
Grouping with BufferingIterator
If HTTP API doesn't allow you setting high number of records per page, use BufferingIterator.
import requests
from bezalel import PaginatedApiIterator, BufferingIterator
for page in BufferingIterator(PaginatedApiIterator(requests.Session(), url=f"http://localhost:5000/page-api",
request_page_number_param_name="pageNumber",
response_page_count_field_name="pageCount",
response_records_field_name="entities"), buffer_size=2):
print(f"Page: {page}")
It will combine multiple pages into one array, so that
Page: [{"key": "val1", ...}, {"key": "val2", ...}, ..., {"key": "val100", ...}, {"key": "val101", ...}, ...]
Page: [{"key": "val200", ...}, {"key": "val201", ...}, ..., {"key": "val300", ...}, {"key": "val301", ...}, ...]
...
This is useful for fetching many records and storing them in fewer files (every file would be bigger).
Iterating over all records
TODO: this API will be improved in future release.
import itertools
import requests
from bezalel import PaginatedApiIterator
all_elems = list(itertools.chain.from_iterable(PaginatedApiIterator(requests.Session(), url=f"https://your/api",
request_page_number_param_name="pageNumber",
response_page_count_field_name="pageCount",
response_records_field_name="entities"))):
print(f"len={len(all_elems)}: {all_elems}")
will print
len=12300: [{"key": "val1", ...}, {"key": "val2", ...}, ...]
Helper function: normalize_with_prototype()
Normalize python dict, so that it has all the fields and only the fields specified in a prototype dict.
from bezalel import normalize_with_prototype
object_from_api = {
"id": 123,
"name:": "John",
"country": "Poland",
"customDict": {
"some": 123,
"complex": 345,
"structure": 546
},
# city is not provided here (but present in prototype)
"pets": [
{"id": 101, "type": "dog", "name": "Barky"},
{"id": 102, "type": "snail"}, # name is not provided here (but present in prototype)
],
"unspecifiedField": 123 # this field is not present in prototype below
}
prototype_from_swagger = {
"id": 0,
"name:": "",
"country": "",
"customDict": {},
"city": "",
"pets": [
{"id": 0, "type": "", "name": ""},
]
}
result = normalize_with_prototype(prototype_from_swagger, object_from_api, pass_through_paths=[".customDict"])
# pass_through_paths is optional and it marks an object as something that should not be normalized
would return
result = {
"id": 123,
"name:": "John",
"country": "Poland",
"customDict": {
"some": 123,
"complex": 345,
"structure": 546
},
"city": None, # city was added
"pets": [
{"id": 101, "type": "dog", "name": "Barky"},
{"id": 102, "type": "snail", "name": None}, # name was added
]
}
Helper function: normalize_dicts()
Normalize list of nested python dicts to a list of one-level dicts.
Example:
from bezalel import normalize_dicts
data = [
{
"id": 1, "name": "John Smith",
"pets": [
{"id": 101, "type": "cat", "name": "Kitty", "toys": [{"name": "toy1"}, {"name": "toy2"}]},
{"id": 102, "type": "dog", "name": "Barky", "toys": [{"name": "toy3"}]}
]
},
{
"id": 2, "name": "Sue Smith",
"pets": [
{"id": 201, "type": "cat", "name": "Kitten", "toys": [{"name": "toy4"}, {"name": "toy5"}, {"name": "toy6"}]},
{"id": 202, "type": "dog", "name": "Fury", "toys": []}
]
},
]
normalize_dicts(data, ["pets", "toys"])
would return:
[{'id': 1, 'name': 'John Smith', 'pets.id': 101, 'pets.type': 'cat', 'pets.name': 'Kitty', 'pets.toys.name': 'toy1'},
{'id': 1, 'name': 'John Smith', 'pets.id': 101, 'pets.type': 'cat', 'pets.name': 'Kitty', 'pets.toys.name': 'toy2'},
{'id': 1, 'name': 'John Smith', 'pets.id': 102, 'pets.type': 'dog', 'pets.name': 'Barky', 'pets.toys.name': 'toy3'},
{'id': 2, 'name': 'Sue Smith', 'pets.id': 201, 'pets.type': 'cat', 'pets.name': 'Kitten', 'pets.toys.name': 'toy4'},
{'id': 2, 'name': 'Sue Smith', 'pets.id': 201, 'pets.type': 'cat', 'pets.name': 'Kitten', 'pets.toys.name': 'toy5'},
{'id': 2, 'name': 'Sue Smith', 'pets.id': 201, 'pets.type': 'cat', 'pets.name': 'Kitten', 'pets.toys.name': 'toy6'},
{'id': 2, 'name': 'Sue Smith', 'pets.id': 202, 'pets.type': 'dog', 'pets.name': 'Fury'}]
Presence of the last record can be controlled by flag return_incomplete_records. If return_incomplete_records=False
then last record in the example would not have been returned.
Additional options:
- jsonify_lists - when set to True, then if a list is encountered (not in main path), it is dumped as a JSON string.
- jsonify_dicts - list of paths for where to expect a dict. That dict will be then dumped as a JSON string.
Metadata
Release files for bezalel 0.0.22
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 |
|---|---|---|---|---|
| bezalel-0.0.22.tar.gz | 14.1 kB | Without provenance | Details for bezalel-0.0.22.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bezalel-0.0.22-py3-none-any.whl | Python 3 | none | any | Details for bezalel-0.0.22-py3-none-any.whl |
Total release size: 26.0 kB
Release files / bezalel-0.0.22.tar.gz
| Download URL | bezalel-0.0.22.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30c85897d1fea5ceeed600e81ad051abee757eaae45f09a63a92fd00d69f5bb7
|
|
BLAKE2b-256 checksum How to use checksums |
861c9234250ab898b27196194431fc1a592941d310cff15b931c185e58cdb80a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.1
|
Release files / bezalel-0.0.22-py3-none-any.whl
| Download URL | bezalel-0.0.22-py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71caad6e5be1a3f4c14ee451e759d3c5ae78ae8bb59610d6dc7866b17899aaa7
|
|
BLAKE2b-256 checksum How to use checksums |
e4873078fefcc405c431fe1d5ee593b822d289b6344edb4a827c75524e70755e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.1
|
Security for bezalel 0.0.22
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.