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. Simple subclasses of types like UUID, str, int, date, and datetime are also stored using their base Postgres type while being returned as their subclass in Python.

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.15.1

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.15.1
File Size Uploaded Provenance Actions
iceaxe-0.15.1.tar.gz 236.3 kB With provenance Details for iceaxe-0.15.1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for iceaxe 0.15.1
File Actions
iceaxe-0.15.1-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.15.1-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.15.1-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.15 CPython 3.15 Linux glibc 2.17+ ARM64 Details for iceaxe-0.15.1-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.15.1-cp315-cp315-macosx_11_0_arm64.whl CPython 3.15 CPython 3.15 macOS 11.0+ ARM64 Details for iceaxe-0.15.1-cp315-cp315-macosx_11_0_arm64.whl
iceaxe-0.15.1-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.15.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.15.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details for iceaxe-0.15.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.15.1-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for iceaxe-0.15.1-cp314-cp314-macosx_11_0_arm64.whl
iceaxe-0.15.1-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.15.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.15.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details for iceaxe-0.15.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.15.1-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for iceaxe-0.15.1-cp313-cp313-macosx_11_0_arm64.whl
iceaxe-0.15.1-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.15.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.15.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details for iceaxe-0.15.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.15.1-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for iceaxe-0.15.1-cp312-cp312-macosx_11_0_arm64.whl
iceaxe-0.15.1-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.15.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
iceaxe-0.15.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64 Details for iceaxe-0.15.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
iceaxe-0.15.1-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for iceaxe-0.15.1-cp311-cp311-macosx_11_0_arm64.whl

Total release size: 4.8 MB

Release files / iceaxe-0.15.1.tar.gz

Download URL iceaxe-0.15.1.tar.gz
Size 236.3 kB
Tags Source
SHA-256 checksum
How to use checksums
610be559b1d091b83988dee5864afa58482c11084a59d0b9b18e30fed4adea4a
BLAKE2b-256 checksum
How to use checksums
4bfc9239d680f9459cab594bfd92068c0ed08b8e2e9a8b61bc9e692ec6684dd8
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 311.2 kB
Tags CPython 3.15 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
1091545ce0ff2ce978d4293b958d637a0fcd5d7f8395b22f451e7ab7b0bab719
BLAKE2b-256 checksum
How to use checksums
dea88908434a9ee1ca608a4a5317846b9dd36e3803466f5685a4d479ea93d671
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp315-cp315-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 308.1 kB
Tags CPython 3.15 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
e5223c4ad9de33be8705891bb2d75ebf7765c59348bbbb280d52015ed4bf8df1
BLAKE2b-256 checksum
How to use checksums
22670aac86184355e4f2982bd1049b4c7a7d3994f08b8e1b1ed6a2e5cf49b75a
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp315-cp315-macosx_11_0_arm64.whl
Size 302.8 kB
Tags CPython 3.15 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4ca647f5a7237f5974207d6ee578a99190017d86c5b7bb0d37bb1ddaa7290ddc
BLAKE2b-256 checksum
How to use checksums
17465d7e5c4089000107e5674b9e3527342cf9d6b8ec36efc7593580d666d49e
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 311.1 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
cab3fdb897d3cc91857ff0dec9e0f6019af1ceb36cc93e2e20c5728ba76d7b8c
BLAKE2b-256 checksum
How to use checksums
545fbf4705a2573f0e29482e9ddeb9e259834215ec79d382aba5c1443c1bd740
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 308.0 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
d5a8c421d6ff639cde16261562b640a981a356da9c63f03f8551862fe043163e
BLAKE2b-256 checksum
How to use checksums
d61ab3e6fcb3451f7285b2afc0e5b29219734f6bbb4116a4a41ef6451e9a950a
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp314-cp314-macosx_11_0_arm64.whl
Size 302.4 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
29aa17241342f2fef02a31b4db8f2f14b470351b72f7ecd3bcb96f9f46c0a89c
BLAKE2b-256 checksum
How to use checksums
6c5e3c9c43070947d0036211afa09859e9c28d12e0580b17e952dca14a3686d2
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 311.3 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
53da00160d2c01839687d2caa72d739dec1d1bb34248c930085adb25ce972273
BLAKE2b-256 checksum
How to use checksums
783473513198685ee6f4a59df9f7bc95cb990e60c75d8405e29987dce47aeb5f
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 308.1 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
222a07d3fc9784658f0bfcb78b4eca02a2ab87cfdc1c56cf0aebf8bf9d9c9219
BLAKE2b-256 checksum
How to use checksums
0510199dfcd8d032ee6fd584c676c4d8b7834c1cb5ba989efc33188a3286e826
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp313-cp313-macosx_11_0_arm64.whl
Size 302.6 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
596e697dc2a7c70c98e3d1e4f40fd6038a5313e72565151c0c86bd1aa0a0faa2
BLAKE2b-256 checksum
How to use checksums
d28ee32f88fe80b480cab67ee47f85ee157972a26f6f9c06f4125895ceb66eba
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 311.3 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
f5be4a61c7dbba34bbadbe1e8895a0981834b0cfbcb7b5ad0d5c2ca6d67b6f5e
BLAKE2b-256 checksum
How to use checksums
1b7dfe0c6c1cd3e63970aff127e0e05c31930a27acfc8e601b18b3835f6e60ea
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 308.1 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
050845a68142ffb6855223495131e81e498f613bc3f5e736db33c5e43d1473aa
BLAKE2b-256 checksum
How to use checksums
7297fbd89079b3206af1f9c8cc0adfba4edc706ccca3239b852946098cb1d9d1
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp312-cp312-macosx_11_0_arm64.whl
Size 302.7 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
7ec215de3df0169ce13a532573dfa1ce9494aa21f6979f20289ad9dc63eb3045
BLAKE2b-256 checksum
How to use checksums
0db339ea3fea4d3a2d38f43afe7d5dd9680f20ed1a3bdbd83d816145b6753202
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 306.7 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
13187134ba6f2a9536bb4bee20b45b834bf9c8c29dd124b22830b631c25ea5c0
BLAKE2b-256 checksum
How to use checksums
64a5459c01dbe02f16fa12511a7cd5983277603aa84b3abd3fec883b8d5a36e2
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 304.0 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
335deab8832c132a6d5ca6cc0feb25fcd78926a75b3a896cd46f39a4b4cda611
BLAKE2b-256 checksum
How to use checksums
20a37eef915c3e0a897d4187948081fbf2a3aeaccecc829dbc146b40c50e2514
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 Oct 26, 2026.

Transparency log

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

Download URL iceaxe-0.15.1-cp311-cp311-macosx_11_0_arm64.whl
Size 298.9 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
7f1944d26e74691731ed6db476e1072e8a950ccc6a660e7e132e66df66445c32
BLAKE2b-256 checksum
How to use checksums
92612df4b1646a9cb3cf8e39a3b290f3e4250432ed71a79024313d28374517a7
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 Oct 26, 2026.

Transparency log

Security for iceaxe 0.15.1

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.15.1.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 Oct 26, 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.15.1 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