Skip to main content

iceaxe

Iceaxe Logo

Python Version Test status

A modern, fast ORM for Python. We have the following goals:

  • 🏎️ Performance: We want to exceed or match the fastest ORMs in Python. We want our ORM to be as close as possible to raw-asyncpg speeds. See the "Benchmarks" section for more.
  • 📝 Typehinting: Everything should be typehinted with expected types. Declare your data as you expect in Python and it should bidirectionally sync to the database.
  • 🐘 Postgres only: Leverage native Postgres features and simplify the implementation.
  • ⚡ Common things are easy, rare things are possible: 99% of the SQL queries we write are vanilla SELECT/INSERT/UPDATEs. These should be natively supported by your ORM. If you're writing really complex queries, these are better done by hand so you can see exactly what SQL will be run.

Iceaxe is used in production at several companies. It's also an independent project. It's compatible with the Mountaineer ecosystem, but you can use it in whatever project and web framework you're using.

For comprehensive documentation, visit https://iceaxe.sh.

To auto-optimize your self hosted Postgres install, check out our new autopg project.

Installation

If you're using poetry to manage your dependencies:

uv add iceaxe

Otherwise install with pip:

pip install iceaxe

Usage

Define your models as a TableBase subclass:

from iceaxe import TableBase

class Person(TableBase):
    id: int
    name: str
    age: int

TableBase is a subclass of Pydantic's BaseModel, so you get all of the validation and Field customization out of the box. We provide our own Field constructor that adds database-specific configuration. For instance, to make the id field a primary key / auto-incrementing you can do:

from iceaxe import Field

class Person(TableBase):
    id: int = Field(primary_key=True)
    name: str
    age: int

Structured JSON values and per-model identifier types also work naturally in table definitions:

from typing import NewType
from uuid import UUID

from iceaxe import Field, TableBase
from pydantic import BaseModel

PersonId = NewType("PersonId", UUID)
OrganizationId = NewType("OrganizationId", UUID)

class Preferences(BaseModel):
    theme: str
    notifications: bool

class Organization(TableBase):
    id: OrganizationId = Field(primary_key=True)

class Person(TableBase):
    id: PersonId = Field(primary_key=True)
    organization_id: OrganizationId
    preferences: Preferences = Field(is_json=True)

person_id = PersonId(UUID("12345678-1234-5678-1234-567812345678"))
organization_id = OrganizationId(UUID("87654321-4321-6789-4321-678943216789"))
preferences = Preferences(theme="dark", notifications=True)

Person(id=person_id, organization_id=organization_id, preferences=preferences)
Person(id=organization_id, organization_id=person_id, preferences=preferences)  # type checker error

Field(is_json=True) will round-trip Pydantic models through a JSON column. NewType identifiers are stored using their underlying Postgres type, so PersonId and OrganizationId are both UUID columns while static type checkers can still flag accidentally swapped IDs.

Prefer NewType for identifiers used only for static type checking: values remain ordinary UUIDs, avoiding subclass reconstruction for every selected ID while retaining normal Pydantic model validation. Simple subclasses of types like UUID, str, int, date, and datetime are also supported when you need a distinct runtime class. Reads return subclass instances, which adds conversion and allocation work. See choosing an identifier type for the performance and runtime tradeoffs.

Okay now you have a model. How do you interact with it?

Databases are based on a few core primitives to insert data, update it, and fetch it out again. To do so you'll need a database connection, which is a connection over the network from your code to your Postgres database. The DBConnection is the core class for all ORM actions against the database.

from iceaxe import DBConnection
import asyncpg

conn = DBConnection(
    await asyncpg.connect(
        host="localhost",
        port=5432,
        user="db_user",
        password="yoursecretpassword",
        database="your_db",
    )
)

The Person class currently just lives in memory. To back it with a full database table, we can run raw SQL or run a migration to add it:

await conn.conn.execute(
    """
    CREATE TABLE IF NOT EXISTS person (
        id SERIAL PRIMARY KEY,
        name TEXT NOT NULL,
        age INT NOT NULL
    )
    """
)

Magic Migrations

For local development or side projects, you can use magic_migrate to automatically sync your database schema with your models:

await conn.magic_migrate("my_project")

If you want to limit the sync to a subset of tables or label the generated revision, you can also pass models=[...] and message="...".

This will:

  1. Compare your current database schema against your model definitions
  2. Generate a migration file if changes are detected
  3. Apply all pending migrations

The migration files are written to your package's migrations/ folder, giving you a history of schema changes.

Recommended workflow for production:

While magic_migrate is convenient for rapid local iteration, we recommend a more controlled approach before merging to production:

  1. Iterate freely during development using magic_migrate
  2. Before merging, reset your database to the production schema state
  3. Run uv run migrate generate once to generate a single, clean migration file
  4. Commit this migration file with your PR

This ensures your production migrations are clean and reviewable, while still giving you the speed of automatic migrations during development.

Inserting Data

Instantiate object classes as you normally do:

people = [
    Person(name="Alice", age=30),
    Person(name="Bob", age=40),
    Person(name="Charlie", age=50),
]
await conn.insert(people)

print(people[0].id) # 1
print(people[1].id) # 2

Because we're using an auto-incrementing primary key, the id field will be populated after the insert. Iceaxe will automatically update the object in place with the newly assigned value.

Updating data

Now that we have these lovely people, let's modify them.

person = people[0]
person.name = "Blice"

Right now, we have a Python object that's out of state with the database. But that's often okay. We can inspect it and further write logic - it's fully decoupled from the database.

def ensure_b_letter(person: Person):
    if person.name[0].lower() != "b":
        raise ValueError("Name must start with 'B'")

ensure_b_letter(person)

To sync the values back to the database, we can call update:

await conn.update([person])

If we were to query the database directly, we see that the name has been updated:

id | name  | age
----+-------+-----
  1 | Blice |  31
  2 | Bob   |  40
  3 | Charlie | 50

But no other fields have been touched. This lets a potentially concurrent process modify Alice's record - say, updating the age to 31. By the time we update the data, we'll change the name but nothing else. Under the hood we do this by tracking the fields that have been modified in-memory and creating a targeted UPDATE to modify only those values.

Selecting data

To select data, we can use a QueryBuilder. For a shortcut to select query functions, you can also just import select directly. This method takes the desired value parameters and returns a list of the desired objects.

from iceaxe import select

query = select(Person).where(Person.name == "Blice", Person.age > 25)
results = await conn.exec(query)

If we inspect the typing of results, we see that it's a list[Person] objects. This matches the typehint of the select function. You can also target columns directly:

query = select((Person.id, Person.name)).where(Person.age > 25)
results = await conn.exec(query)

This will return a list of tuples, where each tuple is the id and name of the person: list[tuple[int, str]].

We support most of the common SQL operations. Just like the results, these are typehinted to their proper types as well. Static typecheckers and your IDE will throw an error if you try to compare a string column to an integer, for instance. A more complex example of a query:

query = select((
    Person.id,
    FavoriteColor,
)).join(
    FavoriteColor,
    Person.id == FavoriteColor.person_id,
).where(
    Person.age > 25,
    Person.name == "Blice",
).order_by(
    Person.age.desc(),
).limit(10)
results = await conn.exec(query)

As expected this will deliver results - and typehint - as a list[tuple[int, FavoriteColor]]

For the common "fetch the first matching model or fail" case, use .one():

from iceaxe import NoObjectFound

try:
    person = await conn.exec(
        select(Person)
        .where(Person.id == 1)
        .one()
    )
except NoObjectFound:
    person = None

.one() only applies to a single full-model select like select(Person). It adds LIMIT 1, returns a single Person instead of list[Person], and raises NoObjectFound if the query returns no rows.

When a query fails, Iceaxe raises IceaxeQueryError with the SQL text and variables attached to the exception message while still preserving the original asyncpg exception type.

Production

Note that underlying Postgres connection wrapped by conn will be alive for as long as your object is in memory. This uses up one of the allowable connections to your database. Your overall limit depends on your Postgres configuration or hosting provider, but most managed solutions top out around 150-300. If you need more concurrent clients connected (and even if you don't - connection creation at the Postgres level is expensive), you can adopt a load balancer like pgbouncer to better scale to traffic. More deployment notes to come.

It's also worth noting the absence of request pooling in this initialization. This is a feature of many ORMs that lets you limit the overall connections you make to Postgres, and re-use these over time. We specifically don't offer request pooling as part of Iceaxe, despite being supported by our underlying engine asyncpg. This is a bit more aligned to how things should be structured in production. Python apps are always bound to one process thanks to the GIL. So no matter what your connection pool will always be tied to the current Python process / runtime. When you're deploying onto a server with multiple cores, the pool will be duplicated across CPUs and largely defeats the purpose of capping network connections in the first place.

Benchmarking

We have basic benchmarking tests in the __tests__/benchmarks directory. To run them, you'll need to execute the pytest suite:

uv run pytest -m integration_tests

Current benchmarking as of October 11 2024 is:

raw asyncpg iceaxe external overhead
TableBase columns 0.098s 0.093s
TableBase full 0.164s 1.345s 10%: dict construction 90%: pydantic overhead

Development

If you update your Cython implementation during development, you'll need to re-compile the Cython code. This can be done with a simple uv sync.

uv sync

Metadata

Release files for iceaxe 0.16.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for iceaxe 0.16.0
File Size Uploaded Provenance Actions
iceaxe-0.16.0.tar.gz 236.9 kB With provenance Details for iceaxe-0.16.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for iceaxe 0.16.0
File Actions
iceaxe-0.16.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.15 CPython 3.15 Linux glibc 2.17+ x86-64 Details for iceaxe-0.16.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.16.0-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.15 CPython 3.15 Linux glibc 2.17+ ARM64 Details for iceaxe-0.16.0-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.16.0-cp315-cp315-macosx_11_0_arm64.whl CPython 3.15 CPython 3.15 macOS 11.0+ ARM64 Details for iceaxe-0.16.0-cp315-cp315-macosx_11_0_arm64.whl
iceaxe-0.16.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for iceaxe-0.16.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.16.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details for iceaxe-0.16.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.16.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for iceaxe-0.16.0-cp314-cp314-macosx_11_0_arm64.whl
iceaxe-0.16.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for iceaxe-0.16.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.16.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details for iceaxe-0.16.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.16.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for iceaxe-0.16.0-cp313-cp313-macosx_11_0_arm64.whl
iceaxe-0.16.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for iceaxe-0.16.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.16.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details for iceaxe-0.16.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.16.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for iceaxe-0.16.0-cp312-cp312-macosx_11_0_arm64.whl
iceaxe-0.16.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for iceaxe-0.16.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.16.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64 Details for iceaxe-0.16.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.16.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for iceaxe-0.16.0-cp311-cp311-macosx_11_0_arm64.whl

Total release size: 4.8 MB

Release files / iceaxe-0.16.0.tar.gz

Download URL iceaxe-0.16.0.tar.gz
Size 236.9 kB
Tags Source
SHA-256 checksum
How to use checksums
0aac2f7a1beef90358d117f9a45f0a7f4c9e6a2b96d45dcfba3e0cdabfd2ec6f
BLAKE2b-256 checksum
How to use checksums
a7beaafc280d73005a868351c9da26e86077644b61b191a5f0acef6c87a0d773
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL iceaxe-0.16.0-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 308.4 kB
Tags CPython 3.15 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
90d4ec8a8cc82e7292983c3a4fb1c3ec9ff7a8b73d296cd50a8757ee8ae55597
BLAKE2b-256 checksum
How to use checksums
160938bf52e89ace43b56b549fd7e2856629b2226daaeea2b1f8d8d3d727c789
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL iceaxe-0.16.0-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 306.4 kB
Tags CPython 3.15 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
0f26eb07063cbe85427074125a244395e9e827f51396fa02afaa7d756e14d56f
BLAKE2b-256 checksum
How to use checksums
3bdf1b7c856a94091c113f3c3d75a05a1275db2428984ed9929b14c9eb25173f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp315-cp315-macosx_11_0_arm64.whl

Download URL iceaxe-0.16.0-cp315-cp315-macosx_11_0_arm64.whl
Size 299.9 kB
Tags CPython 3.15 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
954bb725a30989ee3f23763d269116caa222e340323c6928207ae31ec466e10c
BLAKE2b-256 checksum
How to use checksums
3a088810b64e5e4d219423e113ecbdc3c5793eb76a78f80f1aed496577aca28a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL iceaxe-0.16.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 308.3 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
c864ae0a2f0215e828a9cde4b0068e3ae7ed8f466b8d5bc6a128a332f0e4bddb
BLAKE2b-256 checksum
How to use checksums
eca30acaaf3045cd8e2d0e36afb6544ac0933ff9432c6d60281f94128eb42a94
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL iceaxe-0.16.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 306.2 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
8ff3cb5e14d795a380c5dcf5aee151f91c94f2dce33b947a3c9ede447120f503
BLAKE2b-256 checksum
How to use checksums
3c794cc8dce462c0dbc3e8e1805994891eb2b96aa6b4b6f235219f32d79efa98
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL iceaxe-0.16.0-cp314-cp314-macosx_11_0_arm64.whl
Size 299.7 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
c12a9346eb3363dd668135eb23a5fbe95920784d723af5c0e5dc1205a9ac2147
BLAKE2b-256 checksum
How to use checksums
ae3681f7431c3a63df146c69cb67f1e834bbc746480591820659da05c0fb27a0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL iceaxe-0.16.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 308.5 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
f70b6618b3b178446b417fd5d0df6bfcb567e598fd9e1f33ea621ecb2d37f874
BLAKE2b-256 checksum
How to use checksums
57fc2507e863c81cd806e74e44287a9dbc558ddceb4cfb9fa2597923d8810392
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL iceaxe-0.16.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 306.3 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
caaef74f384e8fec84270b0887e3cf461840d74e1a611627af38c08141c3a05a
BLAKE2b-256 checksum
How to use checksums
a78b963f3106ff02d2786539a0c0e956de72792ca2b7c7c5379a7ebbbc86a92f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL iceaxe-0.16.0-cp313-cp313-macosx_11_0_arm64.whl
Size 299.8 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
f92675058dcd83d803d4c5a28e803286d00529e9d681fbf95d75015941bd6fff
BLAKE2b-256 checksum
How to use checksums
79a11e53a92e71530c6429dd6e0c185b3dc897dd715689352b9c932da8071561
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL iceaxe-0.16.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 308.5 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
de19b0f69337aa1f9a5955ff4ac02bd918ac5092058161c5afadbe34083f7af7
BLAKE2b-256 checksum
How to use checksums
eacfe29b33c3d132b2bede0787456b691500ba70f0a5c48d2d49e29fb7ff94e4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL iceaxe-0.16.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 306.4 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
663bb9b61528b68a244646ab77ef3bde02466bf07d77eb470f563b8b16398d63
BLAKE2b-256 checksum
How to use checksums
1bf28f785481607c7c7247f2143b8ee0ccb1825a81e2237d2597222156ff625e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL iceaxe-0.16.0-cp312-cp312-macosx_11_0_arm64.whl
Size 299.9 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3a9d76e4d65f588e0423e936381cff35860d5a4ed17301060c46ed932f1b8103
BLAKE2b-256 checksum
How to use checksums
02ec34fa7d9443ffba5fa222ae86241f0646002ddeef1854145619431fd5e394
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL iceaxe-0.16.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 304.5 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
8aee5023a66f556f44d4a19c2df5e10a590475529614db998e0cf2a146c1b5eb
BLAKE2b-256 checksum
How to use checksums
9186e40901a166181ec0f9f821c199c1208899e5873dc1d8da6694dbefbb03ba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL iceaxe-0.16.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 302.6 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
fa0c83adacabd8bf38f4ff1e472fb16cb598a5ab28ac7c95d0c7dabf4be09a3d
BLAKE2b-256 checksum
How to use checksums
079418a658ccf84e5d305fafd6fd54fde4ad38839ba6fa14a1e29235c865e80d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / iceaxe-0.16.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL iceaxe-0.16.0-cp311-cp311-macosx_11_0_arm64.whl
Size 296.8 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
131ad4d4160e31ea4d13e90a56b90515aedac610002bf40bd29c501abbb50cd6
BLAKE2b-256 checksum
How to use checksums
3690c8d89b4cc3eb4a64a25430b8c77cc0a406a1368e6f16be48e8b58484f126
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Security for iceaxe 0.16.0

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.

Full provenance

All 16 files in this release have been uploaded with provenance metadata.

Select from 16 files

Attestation for iceaxe-0.16.0.tar.gz

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 Nov 3, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.16.0 This release

16 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page