Readme
pyA2L is an ASAM MCD-2MC processing library written in Python.
If you work with ECUs, ASAP2/A2L is the contract that describes what and how to measure or calibrate. pyA2L helps you parse once, inspect and validate programmatically, automate checks, and export back when needed — all from Python.
Contents
About ASAM MCD-2 MC (ASAP2)
What pyA2L offers
Installation
Getting Started (Quickstart)
Command-line usage
Tips
Examples
Compatibility
Project links
Contributing
Code of Conduct
License
Changelog / Release notes
Acknowledgements
About ASAM MCD-2 MC (ASAP2)
ASAM MCD-2 MC (ASAP2) is the ASAM standard that defines the A2L description format for ECU measurement signals and calibration parameters. In practice, the A2L acts as a contract between ECU software and tools so different vendors can consistently locate data in memory and convert raw values into physical engineering units. Runtime transport (e.g., CCP/XCP) is out of scope of the standard.
For an authoritative overview of the standard, see the ASAM page: https://www.asam.net/standards/detail/mcd-2-mc/
What pyA2L offers
Parse .a2l files and persist them as compact, queryable SQLite databases (.a2ldb) to avoid repeated parse costs.
Programmatic access to ASAP2 entities via SQLAlchemy ORM models (MODULE, MEASUREMENT, CHARACTERISTIC, AXIS_DESCR, RECORD_LAYOUT, COMPU_METHOD/COMPU_TAB, UNIT, FUNCTION, GROUP, VARIANT_CODING, etc.).
Rich inspection helpers in pya2l.api.inspect (e.g., Characteristic, Measurement, AxisDescr, ModPar, ModCommon) to compute shapes, axis info, allocated memory, conversions, and more.
Creator API in pya2l.api.create to programmatically build or augment A2L content (PROJECT, MODULE, MEASUREMENT, CHARACTERISTIC, COMPU_METHOD, AXIS_PTS, RECORD_LAYOUT, GROUP, FUNCTION, etc.).
Validation utilities (pya2l.api.validate) to check common ASAP2 rules and project-specific consistency.
Export .a2ldb content back to A2L text or JSON when needed.
Building blocks for automation: reporting, quality gates, CI checks, and integration with CCP/XCP workflows.
Supported ASAP2 version: 1.7.1
Why pyA2L?
Parse once, query fast: Avoid repeated parser runs by working from SQLite.
Powerful model: Use SQLAlchemy ORM to navigate ASAP2 entities naturally.
Beyond parsing: Inspect derived properties, validate consistency, and export back to A2L.
Automate: Integrate with CI to enforce quality gates on A2L content.
Design highlights
SQLite-backed storage (.a2ldb) with SQLAlchemy models
C++ parser (ANTLR4-based) for fast parsing (2.5 MB/s)
Adaptive flush strategy automatically tunes performance (10% speedup for large files)
High-level inspection helpers in pya2l.api.inspect
Creator API in pya2l.api.create for programmatic A2L generation
Validator framework in pya2l.api.validate yielding structured diagnostics
Export to A2L text or JSON format with complete roundtrip fidelity
Optional CLI (a2ldb-imex) for import/export tasks
Concurrent access via SQLite WAL mode (multiple readers during export)
Learn more about the standard at the ASAM website: https://www.asam.net/standards/detail/mcd-2-mc/wiki/
Installation
Via pip: shell $ pip install pya2ldb IMPORTANT: Package-name is pya2ldb NOT pya2l!!!
From Github:
Clone / fork / download pyA2Ldb repository.
Getting Started (Quickstart)
Parse once, work from SQLite thereafter.
Import a .a2l file and persist it as .a2ldb (SQLite):
from pya2l import import_a2l
session = import_a2l(
"ASAP2_Demo_V161.a2l",
# Optional:
# encoding="utf-8", # default is latin-1
# progress_bar=False, # silence the progress meter
# loglevel="ERROR", # also suppresses progress
# force_overwrite=True, # overwrite existing .a2ldb without prompting
)
# Creates ASAP2_Demo_V161.a2ldb in the working directoryOpen an existing .a2ldb without re-parsing:
from pya2l import open_existing
session = open_existing("ASAP2_Demo_V161") # extension .a2ldb is impliedOr use a context manager so resources are closed deterministically:
from pya2l import open_existing
import pya2l.model as model
with open_existing("ASAP2_Demo_V161") as session:
measurements = session.query(model.Measurement).limit(5).all()Query with SQLAlchemy ORM - List all measurements ordered by name with address and data type:
from pya2l import open_existing
import pya2l.model as model
session = open_existing("ASAP2_Demo_V161")
measurements = (
session.query(model.Measurement)
.order_by(model.Measurement.name)
.all()
)
for m in measurements:
print(f"{m.name:48} {m.datatype:12} 0x{m.ecu_address.address:08x}")When not using with ... as ..., call session.close() when finished so SQLite WAL data is checkpointed and file handles are released.
High-level inspection helpers - Use convenience wrappers from pya2l.api.inspect to access derived info:
from pya2l import open_existing
from pya2l.api.inspect import Characteristic, Measurement, AxisDescr
session = open_existing("ASAP2_Demo_V161")
ch = Characteristic(session, "ASAM.C.MAP.UBYTE.IDENTICAL")
print("shape:", ch.dim().shape)
print("element size:", ch.fnc_element_size(), "bytes")
print("num axes:", ch.num_axes())
me = Measurement(session, "ASAM.M.SCALAR.UBYTE.IDENTICAL")
print("is virtual:", me.is_virtual())
axis = ch.axisDescription("X")
print("axis info:", axis.axisDescription("X"))Create A2L content programmatically - Use the Creator API to build or augment A2L databases:
from pya2l import open_create
from pya2l.api.create import (
ProjectCreator, ModuleCreator, MeasurementCreator,
CharacteristicCreator, CompuMethodCreator
)
session = open_create("MyProject.a2ldb")
# Create project and module
pc = ProjectCreator(session)
project = pc.create_project("MyProject", "Demo ECU Project")
mc = ModuleCreator(session)
module = mc.create_module("MyModule", "Demo Module", project=project)
# Add a conversion method
cmc = CompuMethodCreator(session)
cm = cmc.create_compu_method(
"CM_Voltage", "Voltage conversion", "LINEAR",
"%6.3", "V", module_name="MyModule"
)
cmc.add_coeffs_linear(cm, offset=0.0, factor=0.01) # y = 0.01*x + 0
# Add a measurement
mec = MeasurementCreator(session)
meas = mec.create_measurement(
"BatteryVoltage", "Battery voltage in Volts",
"UWORD", "CM_Voltage", resolution=1, accuracy=0.1,
lower_limit=0.0, upper_limit=20.0,
module_name="MyModule"
)
mec.add_ecu_address(meas, 0x1000)
# Add a characteristic (calibration parameter)
cc = CharacteristicCreator(session)
char = cc.create_characteristic(
"InjectionMap", "Fuel injection map",
"MAP", 0x2000, "RL_InjMap", 0.0, "CM_Voltage",
0.0, 100.0, module_name="MyModule"
)
mc.commit()
db.close()Validate your database
from pya2l import open_existing
from pya2l.api.validate import Validator
session = open_existing("ASAP2_Demo_V161")
vd = Validator(session)
for msg in vd(): # iterate diagnostics
# msg has fields: type (Level), category (Category), diag_code (Diagnostics), text (str)
print(msg.type.name, msg.category.name, msg.diag_code.name, "-", msg.text)Export back to A2L or JSON
from pya2l import export_a2l
# Export to A2L text format
export_a2l("ASAP2_Demo_V161", "exported.a2l")
# Or export to JSON for further processing
from pya2l.imex.json_exporter import export_json
export_json("ASAP2_Demo_V161.a2ldb", "exported.json")Tips
Default import encoding is latin-1; override encoding= if your file differs.
Silence the progress meter via progress_bar=False or loglevel="ERROR".
Python package name is pya2ldb (not pya2l).
See howto for Excel export and other short recipes.
Examples
See pya2l/examples for sample A2L files and scripts.
The Sphinx docs contain a fuller tutorial and HOWTO guides.
Create API and coverage parity
pyA2L offers a Creator API in pya2l.api.create to programmatically build or augment A2L content. The project’s goal is coverage parity: everything you can query via pya2l.api.inspect is intended to be creatable via pya2l.api.create.
Example: creating common entities
from pya2l import open_create
from pya2l.api.create import ModuleCreator
from pya2l.api.inspect import Module
# Open or create a database
session = open_create("MyProject.a2l") # or .a2ldb
mc = ModuleCreator(session)
# Create a module
mod = mc.create_module("DEMO", "Demo ECU module")
# Units and conversions
temp_unit = mc.add_unit(mod, name="degC", long_identifier="Celsius",
display="°C", type_str="TEMPERATURE")
ct = mc.add_compu_tab(mod, name="TAB_NOINTP_DEMO", long_identifier="Demo Tab",
conversion_type="TAB_NOINTP",
pairs=[(0, 0.0), (100, 1.0)], default_numeric=0.0)
# Frames and transformers
fr = mc.add_frame(mod, name="FRAME1", long_identifier="Demo frame",
scaling_unit=1, rate=10, measurements=["ENGINE_SPEED"])
tr = mc.add_transformer(mod, name="TR1", version="1.0",
executable32="tr32.dll", executable64="tr64.dll",
timeout=1000, trigger="ON_CHANGE", inverse="NONE",
in_objects=["ENGINE_SPEED"], out_objects=["SPEED_PHYS"])
# Typedefs and instances
ts = mc.add_typedef_structure(mod, name="TSig", long_identifier="Signal",
size=8)
mc.add_structure_component(ts, name="raw", typedefName="UWORD", addressOffset=0)
inst = mc.add_instance(mod, name="S1", long_identifier="Inst of TSig",
type_name="TSig", address=0x1000)
# Verify with inspect helpers
mi = Module(session)
print("#frames:", len(list(mi.frame.query())))
print("#compu tabs:", len(list(mi.compu_tab.query())))See pya2l/examples/create_quickstart.py for a more complete example.
Command-line usage
A small CLI is provided as a console script named a2ldb-imex:
# Show version (exit 0)
$ a2ldb-imex -V
# Import an A2L (creates .a2ldb next to the input or in CWD with -L)
$ a2ldb-imex -i path/to/file.a2l
# Import with explicit encoding and create DB in current directory
$ a2ldb-imex -i path/to/file.a2l -E latin-1 -L
# Overwrite existing .a2ldb without prompting
$ a2ldb-imex -i path/to/file.a2l -f
# Suppress all output (useful in scripts/CI)
$ a2ldb-imex -i path/to/file.a2l -q
# Export an .a2ldb back to A2L text (stdout by default or -o file)
$ a2ldb-imex -e path/to/file.a2ldb -o exported.a2lCompatibility
Python: 3.11 – 3.15
Platforms: Prebuilt wheels are published for selected platforms. From source, Windows/macOS are supported; Linux may require building native extensions.
Project links
Source code: https://github.com/christoph2/pyA2L
Issue tracker: https://github.com/christoph2/pyA2L/issues
Contributing
Contributions are welcome! Please open an issue to discuss significant changes before submitting a PR. See the existing tests under pya2l/tests and examples under pya2l/examples to get started. Contributors should use pre-commit to run formatting and lint checks before committing; see https://pre-commit.com/ for installation and usage.
Code of Conduct
This project follows a Code of Conduct to foster an open and welcoming community. Please read and abide by it when interacting in issues, discussions, and pull requests.
See CODE_OF_CONDUCT for full details.
Changelog / Release notes
See GitHub Releases: https://github.com/christoph2/pyA2L/releases
1 maintainer
Metadata
1 maintainer
Release files for pya2ldb 1.0.355
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pya2ldb-1.0.355.tar.gz | 16.4 MB | Details |
Built distributions (wheels)
Total release size: 51.5 MB
Release files / pya2ldb-1.0.355.tar.gz
| Download URL | pya2ldb-1.0.355.tar.gz |
|---|---|
| Size | 16.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9f8456fd7c984c7662bfdb1f04b8a3ce5052eef7ac4eeeb84c2a0576beca730
|
|
BLAKE2b-256 checksum How to use checksums |
bc99c6efcde19383e4278a94811b8b0bc4a51e2da140b28d5dd9d08a21692c81
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp315-cp315-win_arm64.whl
| Download URL | pya2ldb-1.0.355-cp315-cp315-win_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.15 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
557b7bbe49be8dee23756cbf2c43218b6e04c2eb09d9cdb09d804986d43b3dce
|
|
BLAKE2b-256 checksum How to use checksums |
26f69a02c32473e0553fa78638a6a98e8dc2abf8946b1a308343068ef900d90f
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp315-cp315-win_amd64.whl
| Download URL | pya2ldb-1.0.355-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f027c7cfc358fbef6ab4b1cbfa1e3a9ef035936f991604f4d1e903f4886220bd
|
|
BLAKE2b-256 checksum How to use checksums |
d4c3303b6283ac0086569133303328a9760bc690a03570c5130535ec53d8dfb0
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pya2ldb-1.0.355-cp315-cp315-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.15 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e87827807f1d9780f6039d4c25e964801801c8ee60f3dadbff169ad2791b2b5e
|
|
BLAKE2b-256 checksum How to use checksums |
1884f0aaf9883099a0eaa5c28823d51900260d989d7733198d9ec17a9190e452
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pya2ldb-1.0.355-cp315-cp315-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.15 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
7ebbb116a7461375117885c24245c1c9bec48e0a181b1237c57dbbdbc3a48957
|
|
BLAKE2b-256 checksum How to use checksums |
4f4a88a5ed5b14b3fb28aa3531c7ea801c8a67f3f50b24c049f526aae12011de
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | pya2ldb-1.0.355-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1f7fe3d667510c26ad4f7a8321703b602fa24b4bd2a93f8853e5b5e1b08feab9
|
|
BLAKE2b-256 checksum How to use checksums |
725fd185160527df73c2ec1e5a5784ad0ea035714b957695a5cdba6b29314cf4
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp314-cp314-win_arm64.whl
| Download URL | pya2ldb-1.0.355-cp314-cp314-win_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.14 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
5d972e007abaaeffb44e47907220b2a3329c561560c6875962df0286d45b49fb
|
|
BLAKE2b-256 checksum How to use checksums |
79dd7ca97fc68c172b29e3df3a2b6dafc07b5c2b4ed5c696db278a41d8aae271
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp314-cp314-win_amd64.whl
| Download URL | pya2ldb-1.0.355-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8abae2e35edf4dc7774674bfe7599e46e11a5bd3cd82ce9d000aa89df4310389
|
|
BLAKE2b-256 checksum How to use checksums |
39545ed4664835f04ac4beb5519ac91dcdda822d287961c802cd77bb110ca72e
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pya2ldb-1.0.355-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
cc9728d9b9473c4c426105d9d9ce894fbbe639be9459d86e45158f6365f74c23
|
|
BLAKE2b-256 checksum How to use checksums |
9a8779e02546601d040be7ac6d7436cb34973a8293bf4d6ccdffb882f8ebda67
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pya2ldb-1.0.355-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e73b664887b86cce0a4c5e539f9755dd79bd7b635d18050987b792e96e71e07a
|
|
BLAKE2b-256 checksum How to use checksums |
52d5f792a1d31e046887ce7ffa9405922b11e766880b56287ecf0cb4697f7c7c
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | pya2ldb-1.0.355-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
40ab6fc9689be60f7632d7f3868d82ba5d30712a5d3115ab51f4b4a8c85af73e
|
|
BLAKE2b-256 checksum How to use checksums |
1f07e440d3900a6a8b73fa8e1f7ff5c966f72dd9a5a98a8f74adc5cace8b037e
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp313-cp313-win_arm64.whl
| Download URL | pya2ldb-1.0.355-cp313-cp313-win_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.13 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
94e58fa827265583ed792ad56f26c2fd52aa58c98f31909bc22757f1d65cdeb3
|
|
BLAKE2b-256 checksum How to use checksums |
c1a525ae93fbd449918a46b8f76af2b51cb40c81697feaa80f882838065c47b5
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp313-cp313-win_amd64.whl
| Download URL | pya2ldb-1.0.355-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
124be4a0393dad8f428ebc7ffa6db65611a2114dcd0c158c82b49edcac4c2276
|
|
BLAKE2b-256 checksum How to use checksums |
2951123d30dda0ba8df2036681e537eaf00792b2946ec9acfb3b4564db12bdd2
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pya2ldb-1.0.355-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
943ff5935992991a2f8dca522190f32aff8c45359b6b671c6086ee870c729a6d
|
|
BLAKE2b-256 checksum How to use checksums |
694eecbd3e86e4def2b5dc97ceba99260330123efbc5a801019016be7e07916c
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pya2ldb-1.0.355-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
2b32d9927cb3c3c33a9eadb8dac1d50824f8a32ebc5954b1144c80b14e67cdd1
|
|
BLAKE2b-256 checksum How to use checksums |
6998c2bc0247be80fdf4aa879c7147928a3351c021971efe646f9fb3e0ac92e5
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pya2ldb-1.0.355-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
608e4e3046170a04f0cb1110f5177c9a2961318b47f02f31d840726930d4c24e
|
|
BLAKE2b-256 checksum How to use checksums |
0cf2b1a03fa534c736760cdab7be68023d672ea98c1d83d54ff22103f0aa94df
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp312-cp312-win_arm64.whl
| Download URL | pya2ldb-1.0.355-cp312-cp312-win_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.12 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
800e6b22038073713b73ccfa71e4fd06f916c1d0380e0bba2dc3caea45a6316b
|
|
BLAKE2b-256 checksum How to use checksums |
7c783dd94cf18e0a3d0b626e518a84ce8a8aab69ae0a69ef24f2199a8d904500
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp312-cp312-win_amd64.whl
| Download URL | pya2ldb-1.0.355-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b1a2c2d8d9d064eef4ac277b5fac3b97640bb6f8374e22a0d51c9dd6e1906a3c
|
|
BLAKE2b-256 checksum How to use checksums |
22b77681f4fe0129f4c236b5b72f553eaf902227ec1c1986b88341f4da4fddac
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pya2ldb-1.0.355-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
8fdfd00222ad1fd2c83681c5a63b6fa7da88b513a2e48cf186aff51df7c476b3
|
|
BLAKE2b-256 checksum How to use checksums |
31c8ce005de95b50373fb637cb2e8d56a95edd5c9cb9c75bd98826e5fa6e26dd
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pya2ldb-1.0.355-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
4e58205395a0e2c27949b53b764e76e60a83456a4996bc159ffc79986fa43566
|
|
BLAKE2b-256 checksum How to use checksums |
98c4c419106e4ed9b6c52d20155779ca892f3b8c78f4baa35ba7053be5c49eda
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pya2ldb-1.0.355-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8e76e51aac2b00d2e6786f0d2ccd7f38c0685328d8e5887882936e851afe7df6
|
|
BLAKE2b-256 checksum How to use checksums |
f4a6c598bd519ee4d0bab60085a20f2c0655efa22bb13b889309dc133631b392
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp311-cp311-win_arm64.whl
| Download URL | pya2ldb-1.0.355-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
019f2e5b01b746b2c7e8d2e5c0f68fc799522d425a27e4c766dae11994644ec2
|
|
BLAKE2b-256 checksum How to use checksums |
fa6ea5f4f9b01153065533d39d9e592e9d75765c7ac18e975fc2de55f3c9ac30
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp311-cp311-win_amd64.whl
| Download URL | pya2ldb-1.0.355-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
89fbc9d16fdd4f9183f26c223b2418f63728b612132a00e8b0e2795049e912c6
|
|
BLAKE2b-256 checksum How to use checksums |
08e4768c44af6841cb9c125106914ffbc1c6fc2c3195d0db42ecd3e446048561
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pya2ldb-1.0.355-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
401078362ad0af1d5c949e8009c312c0e9fcb0ccb6d9f573a2919508a7bbb88c
|
|
BLAKE2b-256 checksum How to use checksums |
918b355f62553f6fddee0ad7f6aab498894b689435c43704197d1786812dee31
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pya2ldb-1.0.355-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
64c0c44f8a8e419bd6a73a7a8e82794bf22ac758dee1d6e5bddef267dc78e1f1
|
|
BLAKE2b-256 checksum How to use checksums |
3f084f8aaca03e82702e7d94c660d2e5003e5f4ea3bea6c5e8b3d61216db7143
|
| 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 Oct 16, 2026.
Transparency logRelease files / pya2ldb-1.0.355-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pya2ldb-1.0.355-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3da044a9fb38eae0ad59ec78219682e860bc89ba123037624fd41e34110f081f
|
|
BLAKE2b-256 checksum How to use checksums |
06e98a4839134a8abc4e9859a73714fb88671ef5dc6e9c9df28739fb545a1022
|
| 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 Oct 16, 2026.
Transparency log
