Skip to main content

Python front-end for 𝚒.

This package exposes 𝚒 components as Python objects. Components compile lazily, execute on CPU or CUDA according to their inputs, and interoperate with i.Tensor, Python scalar/list literals, NumPy arrays, and Torch tensors.

Package-style API

import ilang

Exports:

  • ilang.Component
  • ilang.Tensor
  • ilang.Device
  • ilang.Bench
  • ilang.i

Preferred "DSL-style" API

The package-exported object i acts as a callable "namespace" that enables a more compact style of 𝚒 code. When called, it constructs a Component, but it also re-exposes much of the same package-level API as attributes.

from ilang import i

i("+i~.")   # <ilang.component.Component object at ...>
i.Tensor    # <class 'ilang.tensor.Tensor'>
i.Component # <class 'ilang.component.Component'>
i.Device    # <enum 'Device'>
i.I         # mirrors `ilang.Component.I`

Devices

A Device dictates where data lives and where compuation will run.

i.Device.CPU  # "cpu"
i.Device.CUDA # "cuda"

Tensors

Tensors are immutable multidimensional data arrays.

x = i.Tensor([[1, 2], [3, 4]]) # standard construction does shape-inference on nested list
x = i.Tensor([1, 2, 3, 4], shape=(2, 2)) # flat data with shape also works

Values are stored as float32.

Attributes

x.shape  # tuple[int, ...]
x.device # i.Device.CPU or i.Device.CUDA
x.data   # list[float] (only available on CPU tensors)

Methods

Tensor.to(device i.Device) -> Tensor # gives a new tensor on specified device

# examples:
x.to(i.Device.CUDA)
x.to(i.Device.CPU)
x.to("cuda")
x.to("cpu")

Components

i(expr: str) -> Component parses one 𝚒 expression.

f = i("+ij~i") # row-sum

i.I is the identity component.

Component combinators

Components are combined using combinators. Components are immutable, so combinators each return a new component.

Method forms:

f.compose(g) # wires outputs of the right component into inputs of the left component
f.chain(g)   # wires outputs of the left component into inputs of the right component
f.fanout(g)  # shares inputs pairwise between two components
f.pair(g)    # concatenates the inputs and outputs of two components
f.swap()     # swaps the first two outputs of one component

Operator forms:

f << g # f.compose(g)
f >> g # f.chain(g)
f & g  # f.fanout(g)
f | g  # f.pair(g)
~f     # f.swap()

Example:

matmul = i("ik*kj~ijk") >> i("+ijk~ij")

Execution

out = matmul.exec(x, y)

Component.exec(*inputs: TensorLike, into=None) executes one component.

where TensorLike = Tensor | torch.Tensor | numpy.ndarray | nested Python sequence

Execution device is determined by the input devices. All inputs must use the same device. NumPy/Torch inputs must be contiguous and of dtype float32. Python scalars/lists get promoted to CPU ilang.Tensor.

Output type inference

The output container type and device are inferred from the input. For example, f.exec(torch.tensor([...], device="cuda")) returns an torch.Tensor with device="cuda". This can be overridden with into=: f.exec(nparray, into=i.Tensor).

In general, component execution returns Tuple[Tensor] but is automatically unpacked for single output results.

Shape inference

Component.output_shapes(*inputs) returns one shape tuple per output. Shapes are computed from input shapes without executing any kernels.

Benchmarking

bench = f.bench([x], n_warmups=10, n_runs=100)

bench executes warmup runs, records timed runs, and returns Bench.

Bench fields:

bench.mean       # datetime.timedelta
bench.std        # datetime.timedelta
bench.n_warmups  # int
bench.n_runs     # int
bench.runs       # list[datetime.timedelta]

repr(bench) prints a compact human-readable timing summary.

Errors

Invalid programs, invalid input types, invalid dtypes, non-contiguous arrays, device mismatches, and backend failures raise Python exceptions.

Execution requires all inputs to reside on one device. No implicit CPU/CUDA input synchronization is performed by exec.

CUDA tensor data is not read by repr and is not exposed by .data. Copy to CPU explicitly.

Examples

Native tensor execution:

from ilang import i

f = i.i("+ij~ij")
x = i.Tensor([[1, 2], [3, 4]])
y = f.exec(x)

CUDA tensor execution:

x = i.Tensor([[1, 2], [3, 4]]).to("cuda")
y = f.exec(x)
z = y.to("cpu")

NumPy execution:

import numpy as np

x = np.ones((2, 2), dtype=np.float32)
y = f.exec(x)

Torch CUDA execution:

import torch

x = torch.ones((2, 2), dtype=torch.float32, device="cuda")
y = f.exec(x)

Metadata

Release files for ilang-python 0.1.0

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

Built distributions (wheels)

Table of built distributions (wheels) for ilang-python 0.1.0
File Interpreter ABI Platform
ilang_python-0.1.0-py3-none-manylinux_2_28_x86_64.whl Python 3 none Linux glibc 2.28+ x86-64 Details
ilang_python-0.1.0-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details

Total release size: 1.2 MB

Release files / ilang_python-0.1.0-py3-none-manylinux_2_28_x86_64.whl

Download URL ilang_python-0.1.0-py3-none-manylinux_2_28_x86_64.whl
Size 652.5 kB
Tags Linux glibc 2.28+ x86-64 Python 3
SHA-256 checksum
How to use checksums
663873f7b5396ba8afac8a45495b4285d14670fe695f9cfe3ed2916cd0202544
BLAKE2b-256 checksum
How to use checksums
641f151296da381ffdf56e567e6da582915e03c3149146628e55419b08745968
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 5, 2026.

Transparency log

Release files / ilang_python-0.1.0-py3-none-macosx_11_0_arm64.whl

Download URL ilang_python-0.1.0-py3-none-macosx_11_0_arm64.whl
Size 569.9 kB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3530d81a83702110ba398c6f427e8e04d42ddd8c4949a90c2a66b03dc098e871
BLAKE2b-256 checksum
How to use checksums
e4f1858361d8d95a2bb173d90bea334534d89182df9358dab7e40f39e15ac9eb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 5, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

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