Skip to main content

Python bindings

The aux-py distribution (import aux_py) exposes the implemented Hyperliquid, Lighter, QFEX, and Arcus Rust SDK operations. Owned concrete PyO3 clients wrap the same Rust clients, signing, nonce coordination and transports. Python contains asyncio/context-manager glue, not exchange protocol implementations. Rust SDK crates have no PyO3 dependency.

Coverage

Capability Hyperliquid Python Lighter Python
Market metadata meta(dex=...) order_books(market_id=...)
Native book snapshots l2_book(...) order_book_orders(...)
Recent trades over HTTP Not in the current Rust adapter recent_trades(...)
Account state and positions clearinghouse_state(user, dex=...) account(account_index=... / l1_address=...)
Open orders open_orders(user, dex=...) Authenticated active_orders(market_id=...)
Submission/cancellation order, cancel, cancel_by_cloid, with optional nonce/expiry create_order, cancel_order, with optional expiry/attributes
Public streams Book, trades Book, trades, account
Account streams Clearinghouse state, open orders, order updates, fills Authenticated account orders; public account stream
Local and custom async signers HyperliquidSigner LighterSigner
Offline signing/verification L1 and user-signed actions, action hashes, payloads, address recovery Create/cancel transactions, auth tokens, payloads, signature verification
Exact value helpers validate_hyperliquid_order scale_lighter_decimal
Nonce recovery Rust signer-scoped coordinator and explicit nonce options Rust coordinator, public next_nonce, explicit resync_nonce

This is parity with the operations currently implemented in Rust. Funding/withdrawal submissions, Lighter key registration/grouped batches and other unimplemented Rust operations remain outside scope. Python wraps concrete standard transports and default native auth handlers; generic Rust transport/auth traits are not Python subclass interfaces. Custom signing is available through explicit async callbacks.

QFEX and Arcus

QfexClient and ArcusClient are included in the Python distribution. Each wraps the same native Rust implementation and shares the existing exact conversion, error mapping, cancellable subscription, and client shutdown infrastructure.

from aux_py import QfexClient, ArcusClient, ArcusSigner

async with QfexClient(network="testnet") as qfex:
    metadata = await qfex.refdata(ticker="AAPL-USD")
    book = await qfex.order_book("AAPL-USD")

async with ArcusClient(network="testnet") as arcus:
    markets = await arcus.markets(market="BTC-USD")
    book = await arcus.order_book("BTC-USD")

QFEX authentication takes public_key and secret_key, optionally account_id and builder_code. Authenticated methods are positions, account_balances, user_orders, add_order, cancel_order, and subscribe_account; subscribe(channel, symbol) selects public MDS channels. One-shot add/cancel methods authenticate a fresh trade connection, send once, and close it. Quantity/price inputs accept exact decimal strings or integers; floating-point inputs are rejected.

Arcus writes take signer=ArcusSigner(seed_hex), address, and account_index. place_order(market_metadata, request) and cancel_order(request) accept native dictionaries. Markets, books, trades, account, positions, and open orders are public reads. subscribe(specification) preserves native channel envelopes.

See the QFEX guide and Arcus guide for native units, credentials, supported methods, and pending authenticated testnet verification. The Python suite has 49 tests, including local authenticated peers for both new exchanges.

Build and verify

Python 3.10+, Rust 1.92+, and the checked-in lockfile are required. From connectors/:

python3.12 -m venv .venv-python
.venv-python/bin/pip install -r crates/python/dev-requirements.txt
bash scripts/check-python.sh

AUX_PYTHON=/path/to/venv/bin/python selects another venv. Maturin installs a local development extension. Runtime dependencies are the standard library and compiled extension; Maturin and websockets are development-only. The locally verified interpreter/platform is CPython 3.12.7 on macOS arm64. The release workflow below checks additional interpreters and platforms.

Offline tests exercise all bound operations and stream types, the 44 Hyperliquid and 66 Lighter reference vectors, exact values and unknown JSON numbers, partial batches, auth context, callback context/cancellation, concurrent nonces, ambiguous submissions, errors, overflow and cleanup. bash scripts/check.sh separately verifies the Rust-only feature/dependency matrix. Neither check makes exchange requests or places orders.

# Explicit read-only checks for both testnets; no credentials required.
.venv-python/bin/python crates/python/examples/public_testnet.py

Funded testnet submit/cancel and real authenticated Lighter order-stream verification still need configured credentials. Lighter's local cryptographic primitives remain experimental and unaudited; see the signing notes. Python bindings do not remove those release gates.

Releases

The Python release workflow builds CPython 3.10–3.14 wheels for Linux x86_64 (glibc 2.28+) and macOS arm64 and x86_64, plus a source distribution containing the local Rust workspace dependencies. Each wheel and the source distribution are installed and run through the Python test suite before publication. Windows, Linux arm64, and free-threaded Python wheels are not included in this initial matrix.

Pull requests affecting the build inputs and manual workflow runs build and test artifacts without publishing. Publishing a GitHub release with a tag matching aux-py-v<VERSION> publishes those artifacts to PyPI using Trusted Publishing. Other release tags are ignored. The first version is 0.0.0, with tag aux-py-v0.0.0.

Before the first release:

  1. Create a GitHub Actions environment named pypi in polaris-data/aux.
  2. In your PyPI account's Publishing settings, add a pending GitHub publisher with project name aux-py, owner polaris-data, repository aux, workflow filename release-python.yml, and environment pypi.
  3. Merge the workflow and run Release Python SDK manually on main to check all builds. This run does not publish or reserve the package name.
  4. Publish a GitHub release tagged aux-py-v0.0.0 from the verified commit. The workflow creates the PyPI project on its first successful upload.

For subsequent releases, update both [project].version in pyproject.toml and [workspace.package].version in the root Cargo.toml before tagging. The workflow rejects mismatches between those versions and the release tag. No PyPI API token is required. See PyPI's Trusted Publishing guide for the account setup.

Public reads and streams

import asyncio
from aux_py import HyperliquidClient, LighterClient

async def main():
    async with HyperliquidClient(network="testnet") as client:
        meta = await client.meta()
        async with await client.subscribe_l2_book("ETH") as books:
            book = await anext(books)
            print(book["levels"][0][0]["px"])  # Native decimal string.

    async with LighterClient(network="testnet") as client:
        markets = await client.order_books()
        market = next(m for m in markets["order_books"] if m["status"] == "active")
        async with await client.subscribe_order_book(market["market_id"]) as books:
            event = await anext(books)
            print(event["type"], event["order_book"]["nonce"])

asyncio.run(main())

Constructors can run outside an asyncio loop and make no exchange requests. Testnet is the default; select mainnet explicitly. Override http_url and ws_url together for proxies/local servers; network still determines signing context. Lighter additionally accepts chain_id with custom endpoints.

HyperliquidClient.subscribe(specification) accepts the native Rust subscription dictionary. Convenience methods cover trades, clearinghouse state, open orders, order updates and fills. These generic streams yield native { "channel": ..., "data": ... } envelopes, including subscription acknowledgements. The existing subscribe_l2_book() continues yielding bare native book snapshots and skips acknowledgements/pongs.

Lighter streams retain the complete native envelope, including type, channel, nonce/offset metadata and unknown fields. subscribed/order_book is a snapshot and update/order_book is a delta; zero-size levels remain in deltas. Fresh duplicate subscriptions receive their own snapshot. The SDK does not reconstruct a book. Standard transports reconnect with an explicit recoverable GapError before fresh data; applications own reconciliation after gaps.

All clients and iterators support async with, closed, and idempotent await aclose(). Close shuts down owned subscriptions and cancels pending client work. Only one pending anext() is allowed per iterator; competing reads raise BusyError. Cancelling a started read closes that iterator. Rust cleanup continues if the close await is cancelled or the Python object is dropped. Malformed/native-error/overflow streams and exhausted recovery close with structured exceptions. A recoverable GapError leaves the iterator open. Use explicit context management for deterministic cleanup.

Native values and request dictionaries

Responses retain native field names. Decimal strings stay strings; integer IDs use Python integers, including values beyond 64 bits in unknown JSON fields. Other JSON numbers become decimal.Decimal from their source text. No monetary value is routed through a Python float.

Request dictionaries use the Rust adapters' native wire keys. Floating-point inputs and Decimal objects are rejected; explicitly supply native decimal strings or scaled integers. Input nesting is bounded to reject cycles safely. Examples below illustrate shape and require application-owned account/order values before execution.

from aux_py import HyperliquidClient, HyperliquidSigner

signer = HyperliquidSigner(private_key_hex)  # Native Ethereum-style 32-byte key.
async with HyperliquidClient(signer=signer, account_address=account, network="testnet") as client:
    # Agent identity stays separate from the traded account. vault_address is optional.
    result = await client.order({
        "orders": [{"a": asset, "b": True, "p": "1670.1", "s": "0.0147",
                    "r": False, "t": {"limit": {"tif": "Alo"}}}],
        "grouping": "na",
    }, expires_after=expiry_unix_millis)
    # Preserve the native status/response and every per-item status, including errors.
from aux_py import LighterClient, LighterSigner, scale_lighter_decimal

signer = LighterSigner(native_private_key_hex)  # Native 40-byte little-endian scalar.
async with LighterClient(signer=signer, account_index=account_index,
                         api_key_index=api_key_index, network="testnet") as client:
    result = await client.create_order({
        "MarketIndex": market_id, "ClientOrderIndex": unique_client_order_index,
        "BaseAmount": scale_lighter_decimal(size_text, size_decimals),
        "Price": scale_lighter_decimal(price_text, price_decimals),
        "IsAsk": 1, "Type": 0, "TimeInForce": 2, "ReduceOnly": 0,
        "TriggerPrice": 0, "OrderExpiry": expiry_unix_millis,
    })
    await client.cancel_order({"MarketIndex": market_id, "Index": unique_client_order_index})

Read/query identities remain explicit and need no signer where the native API is public. Trading without configured credentials raises AuthenticationError before network access. Signed fields stay inside Rust until submission; output dictionaries from offline signing are inspectable serialized copies.

Hyperliquid preserves its native batch result, including top-level rejection and mixed item outcomes. Lighter code 200 means submission acceptance, not execution. No trading request is replayed automatically. Lighter timeouts, rejection, malformed responses and cancellation during transport quarantine the shared chain/account/API-key sequence, including across independent client instances. Reconcile pending transactions before explicitly calling resync_nonce(); next_nonce() alone does not reset quarantine. Cross-process coordination remains the application's responsibility.

Signers, callbacks and offline workflows

HyperliquidSigner.sign_action(...) returns a native signed envelope with an explicit nonce. sign_user_action(...) supports offline usdSend and approveAgent primitives; it does not submit those workflows. LighterSigner.sign_transaction("create" / "cancel", request, ...) returns tx_type, native tx_info and digest. Explicit offline nonces are caller-managed. LighterSigner.auth_token(...) and authenticated client.auth_token(deadline) return bearer credentials; deadlines use Unix seconds, while transaction/order expiry uses milliseconds. Do not log tokens or signatures used as auth credentials.

Pure helpers construct immutable HyperliquidSigningPayload or LighterSigningPayload objects: hyperliquid_signing_payload, hyperliquid_user_signing_payload, lighter_transaction_signing_payload, and lighter_auth_signing_payload. Payloads expose canonical digest bytes and native context, support address recovery/signature verification, and can be passed to await signer.sign(payload).

from aux_py import HyperliquidSigner

async def remote_sign(payload):
    # Check payload.network and payload.scheme, then send payload.digest to your
    # signing service. Return native {"r": "0x...", "s": "0x...", "v": 27/28}.
    return await signing_service.sign_hyperliquid(payload)

signer = HyperliquidSigner.remote(signer_address, remote_sign)

LighterSigner.remote(public_key_hex, callback) follows the same pattern, returning an 80-byte Schnorr signature encoded as hex. Its payload also exposes chain/account/API-key indexes and transaction/token purpose. Callbacks execute on the initiating asyncio loop with its contextvars; cancelling native work cancels the callback task. Rust verifies returned signatures against the original payload and declared identity before submission. Callback exceptions become sanitized SigningError values. Local keys and callback internals are excluded from signer repr.

The caller's original Python key string cannot be zeroized by the extension; its Rust input copy is cleared and native key storage follows the Rust signer's behavior. See Lighter's signing notes for limitations of its underlying primitives.

Errors

All errors derive from ConnectorError: ValidationError, AuthenticationError, SigningError, NonceUncertainError, DecodeError, ExchangeError, TransportError, GapError, ClosedError, and BusyError.

ExchangeError exposes venue, http_status, body, native_message, native code where available, and exact extra fields. Server text remains explicitly inspectable but is omitted from exception args/str/repr because it can echo credentials. TransportError includes kind and outcome (not_sent or unknown). Native batch item errors remain in their response rather than being collapsed into a single exception.

Network, hashing and signing work runs in Rust without holding interpreter access. Interpreter access is acquired for Python argument/result conversion and user callbacks. PyO3's owned-class boundary and async integration remain confined to this crate.

Recovery controls

Milestone 5 adds safe-read retry and reconnect policies. Defaults are two extra read attempts, three extra reconnect attempts, 100 ms initial exponential backoff capped at two seconds, and a 30-second connection stability threshold. Configure read_retries, reconnect_retries, initial_backoff_ms, max_backoff_ms, reconnect_stable_ms, heartbeat_interval_ms, idle_timeout_ms and max_message_bytes on either client. Set retry counts to zero for the previous one-attempt/terminal behavior. Existing timeout and buffer controls remain available.

GapError derives from TransportError. Catch it within the stream's context manager, invalidate/reconcile derived state and call anext() again; the iterator stays open. Old buffered frames are cleared before recovery data. Terminal overflow, protocol/size errors, expired replay credentials or exhausted recovery close the iterator. Private Lighter token refresh requires a new authenticated subscription. A plain async for does not suppress gap exceptions.

Client aclose() also shuts down the shared Rust transport and waits for its handshakes, requests and socket drivers. Safe reads honor bounded Retry-After handling; signed trading is never automatically retried, even after timeout/shutdown. The 49-test Python suite covers the existing 110 signing vectors, both new exchange adapters, recovery, budget, backoff cancellation, and no-replay cases. See HARDENING.md for Rust/Python examples and detailed lifecycle contracts.

Metadata

Release files for aux-py 0.0.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 aux-py 0.0.0
File Size Uploaded Provenance Actions
aux_py-0.0.0.tar.gz 211.3 kB With provenance Details for aux_py-0.0.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for aux-py 0.0.0
File Actions
aux_py-0.0.0-cp314-cp314-manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ x86-64 Details for aux_py-0.0.0-cp314-cp314-manylinux_2_28_x86_64.whl
aux_py-0.0.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for aux_py-0.0.0-cp314-cp314-macosx_11_0_arm64.whl
aux_py-0.0.0-cp314-cp314-macosx_10_12_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.12+ x86-64 Details for aux_py-0.0.0-cp314-cp314-macosx_10_12_x86_64.whl
aux_py-0.0.0-cp313-cp313-manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64 Details for aux_py-0.0.0-cp313-cp313-manylinux_2_28_x86_64.whl
aux_py-0.0.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for aux_py-0.0.0-cp313-cp313-macosx_11_0_arm64.whl
aux_py-0.0.0-cp313-cp313-macosx_10_12_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.12+ x86-64 Details for aux_py-0.0.0-cp313-cp313-macosx_10_12_x86_64.whl
aux_py-0.0.0-cp312-cp312-manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64 Details for aux_py-0.0.0-cp312-cp312-manylinux_2_28_x86_64.whl
aux_py-0.0.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for aux_py-0.0.0-cp312-cp312-macosx_11_0_arm64.whl
aux_py-0.0.0-cp312-cp312-macosx_10_12_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.12+ x86-64 Details for aux_py-0.0.0-cp312-cp312-macosx_10_12_x86_64.whl
aux_py-0.0.0-cp311-cp311-manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64 Details for aux_py-0.0.0-cp311-cp311-manylinux_2_28_x86_64.whl
aux_py-0.0.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for aux_py-0.0.0-cp311-cp311-macosx_11_0_arm64.whl
aux_py-0.0.0-cp311-cp311-macosx_10_12_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.12+ x86-64 Details for aux_py-0.0.0-cp311-cp311-macosx_10_12_x86_64.whl
aux_py-0.0.0-cp310-cp310-manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64 Details for aux_py-0.0.0-cp310-cp310-manylinux_2_28_x86_64.whl
aux_py-0.0.0-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for aux_py-0.0.0-cp310-cp310-macosx_11_0_arm64.whl
aux_py-0.0.0-cp310-cp310-macosx_10_12_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.12+ x86-64 Details for aux_py-0.0.0-cp310-cp310-macosx_10_12_x86_64.whl

Total release size: 68.9 MB

Release files / aux_py-0.0.0.tar.gz

Download URL aux_py-0.0.0.tar.gz
Size 211.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d7bb66a894d7d56dc5e30e564f5ace58eaf1df3a1df15bc20d94086791cddb11
BLAKE2b-256 checksum
How to use checksums
e171b806535fd26ee959480f9f07c2badd6d9ea75fcf60728baf2c7c4f11ccda
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp314-cp314-manylinux_2_28_x86_64.whl

Download URL aux_py-0.0.0-cp314-cp314-manylinux_2_28_x86_64.whl
Size 4.8 MB
Tags CPython 3.14 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
a811497c3f71073f7a9f03da17f822eef54298837a19dbc814578410d03c26eb
BLAKE2b-256 checksum
How to use checksums
91c298d80f9e98bf3092c3f6452424d1c31f2cc1147534e3bd25869b2154eedd
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL aux_py-0.0.0-cp314-cp314-macosx_11_0_arm64.whl
Size 4.4 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
f4856fc516dd82f8c3fa6d7196960542a80a2f818f98bffab55017ffba6b6a8f
BLAKE2b-256 checksum
How to use checksums
bb6b772016655ecf9457f797d79a6689f054dd53462cc8db8efa7aa270bc9313
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp314-cp314-macosx_10_12_x86_64.whl

Download URL aux_py-0.0.0-cp314-cp314-macosx_10_12_x86_64.whl
Size 4.5 MB
Tags CPython 3.14 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
d82d96468ca537a6beae4ba97085d3a6ce4ab60afa0d2f4dea00b4bfaf48af83
BLAKE2b-256 checksum
How to use checksums
ad0ddcf7d5a3db0e1d601c574efd7cbad08763b74285a07c866226f5a4960f38
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp313-cp313-manylinux_2_28_x86_64.whl

Download URL aux_py-0.0.0-cp313-cp313-manylinux_2_28_x86_64.whl
Size 4.8 MB
Tags CPython 3.13 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
47facbee1366ee2f72e4970971f800c808c437fe95fb003745789913e3810047
BLAKE2b-256 checksum
How to use checksums
4cfd9632deeaa1638e79e56deaa2842368a890d1b71f9a2aa9d5de76b5a91486
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL aux_py-0.0.0-cp313-cp313-macosx_11_0_arm64.whl
Size 4.4 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
2e60e7e6e1fa7d4bf880e86d012541e3b8862bf5a5b43b15ef34ebdc5056b7d6
BLAKE2b-256 checksum
How to use checksums
385e08a860c502eb766d94b36683e1f90682a177971c8e207c756238ee6c4871
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp313-cp313-macosx_10_12_x86_64.whl

Download URL aux_py-0.0.0-cp313-cp313-macosx_10_12_x86_64.whl
Size 4.5 MB
Tags CPython 3.13 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
1be260519e3891af59e60f7865f70e3f23be02b221ef4056bc706f7f87150ef0
BLAKE2b-256 checksum
How to use checksums
90261f0bdd025ca18c8834f47a61dfce127b7cec771bc133f7898a564d0eaaa2
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp312-cp312-manylinux_2_28_x86_64.whl

Download URL aux_py-0.0.0-cp312-cp312-manylinux_2_28_x86_64.whl
Size 4.8 MB
Tags CPython 3.12 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
8cb75a81f5f7e05a2973c72c5fab92b8a14638945c33e18ea1ebf1e62de03008
BLAKE2b-256 checksum
How to use checksums
74c99e17b8bb1cb628aa18342cab12f76176f1794c929954604b37d09491919d
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL aux_py-0.0.0-cp312-cp312-macosx_11_0_arm64.whl
Size 4.4 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
406f30ab663cf0b39a8d9eada84ea91412ebc62bfd8ea638906152168a12449b
BLAKE2b-256 checksum
How to use checksums
223c069f81899e8638ea60bd4fdf38b7574bf65b89fc99d0caa34476623967f3
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp312-cp312-macosx_10_12_x86_64.whl

Download URL aux_py-0.0.0-cp312-cp312-macosx_10_12_x86_64.whl
Size 4.5 MB
Tags CPython 3.12 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
fa60f6c93c29224bc47b369ae13b2e9cc90fae1c36cd07b7fc7f2f53b5ee4197
BLAKE2b-256 checksum
How to use checksums
94767b92cf92724366e6976e3a2844104c6df9403a581cb14179c12e8936a361
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp311-cp311-manylinux_2_28_x86_64.whl

Download URL aux_py-0.0.0-cp311-cp311-manylinux_2_28_x86_64.whl
Size 4.8 MB
Tags CPython 3.11 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
2801f8d25763ad101180d0f10fea8a485ef8af91584c478d9097e0700cea2c8a
BLAKE2b-256 checksum
How to use checksums
4238975e835f04e046e729be7c7977dd3fbdaea745b5e7ab3f8da39d500ca345
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL aux_py-0.0.0-cp311-cp311-macosx_11_0_arm64.whl
Size 4.4 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
6edaa17549c0c4e69c1267617c7f6e9adbb0c7c1953ee4937fbeb6ac23d692db
BLAKE2b-256 checksum
How to use checksums
4b8841c2bbf2f92aedf1010b8b0e3d088a2e3c718f9feb76f016ad134c97e3ac
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp311-cp311-macosx_10_12_x86_64.whl

Download URL aux_py-0.0.0-cp311-cp311-macosx_10_12_x86_64.whl
Size 4.5 MB
Tags CPython 3.11 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
6528dd24de11d15c2ae107d103d85bbf3aa5b4d5931f57f5db0a7ef2dd895475
BLAKE2b-256 checksum
How to use checksums
8776645d40884b0df9837b01cb7069d51ee22d8e801c52a456b8afec17caa9e7
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp310-cp310-manylinux_2_28_x86_64.whl

Download URL aux_py-0.0.0-cp310-cp310-manylinux_2_28_x86_64.whl
Size 4.8 MB
Tags CPython 3.10 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
654ebdbb802b02f4bb651e102de846c4373a6dcbb38783a472bd7b9ed1959d94
BLAKE2b-256 checksum
How to use checksums
d34b88f2a052a28ca9b9da447a06aaec0cb2e756f2ea75fed5a078791a083eec
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp310-cp310-macosx_11_0_arm64.whl

Download URL aux_py-0.0.0-cp310-cp310-macosx_11_0_arm64.whl
Size 4.4 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
245375ed18ea36c20874bb6ef86cb7d406f8d9177121cfad175d11ce506dd424
BLAKE2b-256 checksum
How to use checksums
9d3db533bdb5d7ee7a5a53560b931c8dc8f2142981a5e6e083d8faa0ed50c0e3
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 31, 2026.

Transparency log

Release files / aux_py-0.0.0-cp310-cp310-macosx_10_12_x86_64.whl

Download URL aux_py-0.0.0-cp310-cp310-macosx_10_12_x86_64.whl
Size 4.5 MB
Tags CPython 3.10 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
9fb4302a46388d349eca9efff3a3ee6d66cc955e8607a1724da019fe71ad2eda
BLAKE2b-256 checksum
How to use checksums
67daac0a8552e166a95857f24d4e3a762b598d93d180d5e6c8b120c04a59f344
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 31, 2026.

Transparency log

Security for aux-py 0.0.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 aux_py-0.0.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 Oct 31, 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.0.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