quantilica-core: Fundação de infraestrutura para projetos Quantilica
Biblioteca de utilitários domain-neutral que serve como base para todos os coletores e pipelines Quantilica. Centraliza rede resiliente, armazenamento atômico, proveniência de dados e logging estruturado — permitindo que cada pacote de domínio foque exclusivamente na lógica de sua fonte de dados.
Instalação
pip install quantilica-core
Com uv:
uv add quantilica-core
Uso Rápido
from quantilica.core.http import HttpClient
from quantilica.core.storage import LocalStorage
from quantilica.core.manifests import DownloadManifest
# Cliente HTTP com retry automático
client = HttpClient(attempts=3)
response = client.get("https://api.ibge.gov.br/...")
# Escrita atômica em disco
storage = LocalStorage("dados/raw")
stat = storage.write_bytes("sidra/tabela.csv", response.content)
# Registro de proveniência (SHA-256)
manifest = DownloadManifest.from_file(
source_id="ibge",
dataset_id="sidra-1234",
url="https://...",
file_path=stat.path,
producer="sidra-fetcher",
)
manifest.write_json(stat.path.with_suffix(".manifest.json"))
Módulos
| Módulo | Descrição |
|---|---|
http |
HttpClient e AsyncHttpClient com backoff exponencial e jitter |
retry |
Lógica de retry configurável para falhas de rede e erros transientes |
storage |
LocalStorage para gerenciar artefatos brutos e processados atomicamente |
manifests |
DownloadManifest e ExecutionManifest para rastreabilidade completa |
metadata |
Modelos MetadataCatalog, Source, Dataset para interoperabilidade |
logging |
Logging estruturado via get_logger e log_step |
exceptions |
Hierarquia padrão: FetchError, ParseError, StorageError |
Princípios de Design
- Neutralidade de domínio — o core nunca sabe o que é IBGE, DATASUS ou INMET.
- Leveza — dependências mínimas no núcleo; integrações pesadas são extras opcionais.
- Estabilidade — alta cobertura de testes em todos os componentes de infraestrutura.
- DX — APIs tipadas e tratamento de erros consistente em toda a organização.
Desenvolvimento
git clone https://github.com/Quantilica/quantilica-core.git
cd quantilica-core
uv sync --dev
uv run pytest
Licença
MIT — veja LICENSE.
Metadata
Release files for quantilica-core 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| quantilica_core-0.3.2.tar.gz | 39.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quantilica_core-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 74.2 kB
Release files / quantilica_core-0.3.2.tar.gz
| Download URL | quantilica_core-0.3.2.tar.gz |
|---|---|
| Size | 39.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4c6e90b23d9bf21524aa9acb24feb6d2e11ab2a3a99674fa47a86ef10bd7cb2
|
|
BLAKE2b-256 checksum How to use checksums |
a7099d1908805ed4c0e8b9bb246937397d5202a9c7381dddf33caf6541202c54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.
Transparency logRelease files / quantilica_core-0.3.2-py3-none-any.whl
| Download URL | quantilica_core-0.3.2-py3-none-any.whl |
|---|---|
| Size | 35.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52dcd5ae48c250d8fa8531d543b8eea6fec772fb0f0d9205fb212813c35df862
|
|
BLAKE2b-256 checksum How to use checksums |
5fb2064eeea1bd63a7bbd63f5b5d9f4be86df719aabd0e43bf05e57134458ad0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 31, 2026.
Transparency log