ai4icore-core
Consolidated utility libraries for AI4ICore microservices. A single installable package that bundles what used to live across ten standalone libraries — constants, env, exceptions, logging, telemetry, observability, model management, service base, bootstrap, and email.
Installation
pip install ai4icore-core
Subpackages
| Subpackage | Purpose |
|---|---|
ai4icore_core.bootstrap |
FastAPI app bootstrap helpers (cache, database, redis, schemas, versioning) |
ai4icore_core.constants |
Static error codes, messages, and back-compat re-exports |
ai4icore_core.email |
Provider-agnostic transactional email client (SMTP, console, pluggable) |
ai4icore_core.env |
Pydantic-based environment / settings |
ai4icore_core.exceptions |
Shared exception hierarchy, response envelope, FastAPI handlers |
ai4icore_core.logging |
Structured JSON logging with trace correlation |
ai4icore_core.model_management |
Model management client, Triton inference, FastAPI middleware |
ai4icore_core.observability |
Prometheus metrics, dashboards, middleware |
ai4icore_core.service_base |
App factory, health, rate limit, service registry, inference headers |
ai4icore_core.telemetry |
OpenTelemetry tracing, Jaeger / OpenSearch query clients |
Usage
from ai4icore_core.env import app_env
from ai4icore_core.logging import get_logger, register_logging_plugin
from ai4icore_core.exceptions import register_exception_handlers
from ai4icore_core.observability import ObservabilityPlugin, PluginConfig
from ai4icore_core.telemetry import register_telemetry_plugin, TelemetryConfig
from ai4icore_core.service_base import create_inference_app
See each subpackage's source for the full surface.
Requirements
- Python
>= 3.11
License
MIT — see LICENSE.
Links
Metadata
Release files for ai4icore-core 1.1.9
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 |
|---|---|---|---|---|
| ai4icore_core-1.1.9.tar.gz | 47.0 kB | Without provenance | Details for ai4icore_core-1.1.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ai4icore_core-1.1.9-py3-none-any.whl | Python 3 | none | any | Details for ai4icore_core-1.1.9-py3-none-any.whl |
Total release size: 111.2 kB
Release files / ai4icore_core-1.1.9.tar.gz
| Download URL | ai4icore_core-1.1.9.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f6f3530ed3ac929967a3ddeaad5b82b206a800354c67b10b5ec9ed3998ae1d4
|
|
BLAKE2b-256 checksum How to use checksums |
e79c68c4158016fa9c97a6e730d368c1ab51a4970f4fe758a2cc004e912b64e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / ai4icore_core-1.1.9-py3-none-any.whl
| Download URL | ai4icore_core-1.1.9-py3-none-any.whl |
|---|---|
| Size | 64.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5fd42547a2177307eb4ec4d7d6b7cb17ba4b0a461fe839b032db4833e144df5
|
|
BLAKE2b-256 checksum How to use checksums |
2a2170c197851635cf42a4fdc8daf245393d5538c3d276b20b19bed5c3d5c398
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for ai4icore-core 1.1.9
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.