Skip to main content

typeline

PyPi Release CI Python Versions basedpyright mypy uv Ruff

Write dataclasses to delimited text formats and read them back again.

Headers are matched to fields by name, values are typed by the fields' annotations, and custom formats, comments, extra columns, and compressed files are supported. A native engine reads and writes str, int, float, and bool fields, dates, times, UUIDs, decimals, enums, and literals itself, and hands fields that hold JSON, such as lists, dicts, and nested dataclasses, to msgspec.

Installation

The package can be installed with pip:

pip install typeline

Quickstart

Defining a Record

from dataclasses import dataclass

@dataclass
class MyData:
    field1: int
    field2: str
    field3: float | None

Writing

from pathlib import Path
from tempfile import TemporaryDirectory

from typeline import TsvWriter

temp_dir = TemporaryDirectory()
path = Path(temp_dir.name) / "data.tsv"
records = [MyData(10, "test1", 0.2), MyData(20, "test2", None)]

with TsvWriter.from_path[MyData](path, header=True) as writer:
    writer.write_all(records)

assert path.read_text() == "field1\tfield2\tfield3\n10\ttest1\t0.2\n20\ttest2\t\n"

write_all writes records in order, and write writes one. With header=True, a writer writes its header once: before its first record, or alone when there are no records. Without it, the header is written by calling write_header.

Reading

from typeline import TsvReader

with TsvReader.from_path[MyData](path) as reader:
    assert list(reader) == records

A reader expects a header by default, and matches its columns to fields by name, in any order. Pass header=False to read columns in field order. A field that cannot be read raises a ValueError naming the field, its type, its text, and its line, and so does a row with the wrong number of columns. A reader from from_path closes its file once it is read to the end, so reading everything into a list needs no with block.

assert list(TsvReader.from_path[MyData](path)) == records

Any Text Stream

To use an open text stream instead of a path, subscript the reader or writer class itself. Lines end at \n, \r\n, or a lone \r, however the stream was opened.

Leaving the with block closes the stream.

from io import StringIO

with TsvReader[MyData](StringIO("10\ttest1\t0.2\n"), header=False) as reader:
    assert list(reader) == [MyData(10, "test1", 0.2)]

Decoding a Line

A reader's decode reads one record from a line of text, just as the reader reads each record of its file, with its delimiter and other options. It reads nothing from the reader's stream, so one reader can decode many lines, which is much faster than building a reader for each. A reader built on an empty stream has no header, so it decodes columns in field order. Blank lines around the record are skipped, and blank text, a comment, text holding more than one record, or text ending inside a quoted field is refused with a ValueError.

reader = TsvReader[MyData](StringIO())

assert reader.decode("10\ttest1\t0.2\n") == MyData(10, "test1", 0.2)

Files

from_path reads and writes UTF-8, skips a byte order mark, and ends lines with os.linesep. It reads gzip, bzip2, and xz files, which it recognizes by their contents, and writes them when the path ends in .gz, .bz2, or .xz. It opens a path only once, so it also reads and writes pipes such as FIFOs, /dev/stdin, and /dev/stdout.

with TsvWriter.from_path[MyData](f"{path}.gz") as writer:
    writer.write(MyData(10, "test1", 0.2))

with TsvReader.from_path[MyData](f"{path}.gz", header=False) as reader:
    assert list(reader) == [MyData(10, "test1", 0.2)]

Missing Values

None is written as the none_field, an empty field by default. When read, an empty field is None if the field allows None, and "" if it is a str. Set none_field, e.g. to "NA", when an optional text field must tell "" and None apart. A codec's missing text, as typeline.codecs.nullable sets, takes the place of none_field for its fields.

Comments

A reader skips lines that start with any of its comment_prefixes, and hands each one to on_comment as a Comment with its line number. A writer writes comments with write_comment, so comments can be passed straight from a reader to a writer and keep their places. Comments written before the header stay above it. Readers and writers take lines starting with # as comments by default.

path.write_text("# made by a tool\nfield1\tfield2\tfield3\n10\ttest1\t0.2\n")

with (
    TsvWriter.from_path[MyData](f"{path}.copy", header=True) as writer,
    TsvReader.from_path[MyData](path, on_comment=writer.write_comment) as reader,
):
    writer.write_all(reader)

assert Path(f"{path}.copy").read_text() == path.read_text()

Extra Columns

A record can end with an ExtraColumns field, which holds as text the columns no other field takes, in file order. Readers fill it, writers write it back, and a header only needs to name the other fields.

from typeline import ExtraColumns

@dataclass
class Region:
    name: str
    start: int
    extra: ExtraColumns = ()

path.write_text("exon1\t10\n\nexon2\t20\t0.9\tHIGH\n")

with TsvReader.from_path[Region](path, header=False) as reader:
    assert list(reader) == [Region("exon1", 10), Region("exon2", 20, ("0.9", "HIGH"))]

A record can instead end with a NamedExtraColumns[T] field, which holds those columns as a dict[str, T] keyed by their names in the header, in file order. Each column is read and written as a field of type T would be, codecs included. Readers need a header to name the columns, and writers name them in the header after the other fields, as the first record written names them, so every record must name the same columns.

from dataclasses import field

from typeline import NamedExtraColumns

@dataclass
class Bin:
    size: int
    counts: NamedExtraColumns[int] = field(default_factory=dict)

path.write_text("size\tall.fr\tall.rf\n187\t4123\t12\n")

with TsvReader.from_path[Bin](path) as reader:
    assert list(reader) == [Bin(187, {"all.fr": 4123, "all.rf": 12})]

Counter Columns

A CounterColumns[E] field is a Counter[E] held in one column per member of the enum E, each named after its member's value, which must be text. A record may have several such fields, as long as no two columns share a name. Writers write every member's count in enum order, where the field sits among the other fields. Readers find the member columns by name in a header, wherever they sit, or in enum order at the field's place when there is no header. Every member needs a column, and every count must be a non-negative integer.

from collections import Counter
from enum import StrEnum

from typeline import CounterColumns

class Base(StrEnum):
    A = "A"
    C = "C"
    G = "G"
    T = "T"

@dataclass
class Pileup:
    position: int
    counts: CounterColumns[Base]

with TsvWriter.from_path[Pileup](path) as writer:
    writer.write_header()
    writer.write(Pileup(100, Counter({Base.A: 12, Base.G: 3})))

assert path.read_text() == "position\tA\tC\tG\tT\n100\t12\t0\t3\t0\n"

path.write_text("position\tT\tG\tC\tA\n101\t2\t0\t0\t9\n")

with TsvReader.from_path[Pileup](path) as reader:
    assert list(reader) == [Pileup(101, Counter({Base.A: 9, Base.T: 2, Base.C: 0, Base.G: 0}))]

With an ExtraColumns field, the columns that are neither fields nor member columns are kept as extra columns.

Column Names

A column is named after its field, unless rename gives it another name. Writers can write these names in the header, and readers will match a pre-existing header to them, in any column order. A column name can be any text, like %GC or mean depth, and can be made at runtime too.

@dataclass
class Coverage:
    sample: str
    gc: float
    frac_below_min: float

min_depth = 20
rename = {"gc": "%GC", "frac_below_min": f"frac_below_{min_depth}x"}

with TsvWriter.from_path[Coverage](path, rename=rename) as writer:
    writer.write_header()
    writer.write(Coverage("s1", 41.2, 0.03))

assert path.read_text() == "sample\t%GC\tfrac_below_20x\ns1\t41.2\t0.03\n"

with TsvReader.from_path[Coverage](path, rename=rename) as reader:
    assert list(reader) == [Coverage("s1", 41.2, 0.03)]

A field has one column, so once it is given another name, that name replaces the field's name and the old one is retired. Names are checked when a reader or writer is built. If you name a column for something that is not a field, for an ExtraColumns or CounterColumns field, or give two columns the same name, then an exception is raised. Without a header, columns are read in field order and rename has no effect. A name starting with a comment prefix, like #chrom, is quoted when it starts a header, unless the reader and writer are given comment_prefixes that it does not start with, like ["##"].

Turning Off Quoting

Readers and writers quote fields with " as CSV does, so text can hold the delimiter and line breaks. For formats without quoting, quoting=False reads and writes " as ordinary text. Without quoting, a writer refuses text that holds the delimiter or a line break with a ValueError.

with TsvWriter.from_path[Region](path, quoting=False) as writer:
    writer.write(Region('"exon1', 10, ('say "hi"',)))

assert path.read_text() == '"exon1\t10\tsay "hi"\n'

with TsvReader.from_path[Region](path, header=False, quoting=False) as reader:
    assert list(reader) == [Region('"exon1', 10, ('say "hi"',))]

Custom Field Formats

str fields are written as they are, int and float fields as JSON numbers, and bool fields as true and false, and each reads back only such text, so 12.0 is not an int and True is not a bool. A union of plain types, like int | str, reads its text as the first of bool, int, float, and str that fits. Dates, times, UUIDs, decimals, enums, and literals are written as their usual text too, and lists, tuples, sets, dicts, and nested dataclasses as JSON. For any other text format, a FieldCodec reads a field from its text and writes it back, chosen by the field's type. The value a codec reads is the field's value as it is, so a codec returns the field's type. Helpers in typeline.codecs cover common formats. Among them, nan gives NaN and the infinities their own text, like ?, where a float field would write nan, inf, and -inf.

from datetime import date

from typeline import Codecs
from typeline.codecs import boolean, delimited

@dataclass
class Visit:
    patient: str
    seen: date
    consented: bool
    blocks: list[int]

codecs: Codecs = {
    bool: boolean(true="Y", false="N"),
    list[int]: delimited(int, sep=";"),
}

with TsvWriter.from_path[Visit](path, codecs=codecs) as writer:
    writer.write(Visit("P-001", date(2026, 9, 29), True, [3, 1, 4]))

assert path.read_text() == "P-001\t2026-09-29\tY\t3;1;4\n"

with TsvReader.from_path[Visit](path, header=False, codecs=codecs) as reader:
    assert list(reader) == [Visit("P-001", date(2026, 9, 29), True, [3, 1, 4])]

Custom types nested anywhere inside a field, like a list[Interval], are handled by enc_hook, which turns such an object into builtin values, and dec_hook, which builds it back from them. The hooks apply to the fields msgspec handles, and each raises NotImplementedError for types it does not handle.

class Interval:
    def __init__(self, start: int, end: int) -> None:
        self.start = start
        self.end = end

    def __eq__(self, other: object) -> bool:
        return isinstance(other, Interval) and (self.start, self.end) == (other.start, other.end)

def enc_hook(obj: object) -> object:
    if isinstance(obj, Interval):
        return [obj.start, obj.end]
    raise NotImplementedError

def dec_hook(kind: type, obj: object) -> object:
    if kind is Interval:
        return Interval(*obj)
    raise NotImplementedError

@dataclass
class Target:
    gene: str
    intervals: list[Interval]

with TsvWriter.from_path[Target](path, enc_hook=enc_hook) as writer:
    writer.write(Target("BRCA1", [Interval(1, 9), Interval(20, 25)]))

assert path.read_text() == "BRCA1\t[[1,9],[20,25]]\n"

with TsvReader.from_path[Target](path, header=False, dec_hook=dec_hook) as reader:
    assert list(reader) == [Target("BRCA1", [Interval(1, 9), Interval(20, 25)])]

Your Own Format

Subclass a reader to give a format its own defaults. A format with another delimiter, which must be one ASCII character, subclasses a reader or writer with it, e.g. class PipeReader(DelimitedDataReader[RecordType], delimiter="|").

from typing import TextIO

from typing_extensions import Unpack

from typeline import ReaderOptions, RecordType
from typeline.codecs import key_value

class VcfLikeReader(TsvReader[RecordType]):
    def __init__(self, handle: TextIO, /, **options: Unpack[ReaderOptions]) -> None:
        defaults: ReaderOptions = {
            "codecs": {dict[str, str]: key_value()},
            "header": False,
            "none_field": ".",
        }
        super().__init__(handle, **(defaults | options))

@dataclass
class Site:
    chrom: str
    pos: int
    ident: str | None
    info: dict[str, str]

path.write_text("#CHROM\tPOS\tID\tINFO\nchr1\t100\t.\tDP=10;AF=0.5\n")

with VcfLikeReader.from_path[Site](path) as reader:
    assert list(reader) == [Site("chr1", 100, None, {"DP": "10", "AF": "0.5"})]

Type checkers see VcfLikeReader.from_path[Site](...) as a TsvReader[Site], its closest built-in reader. A subclass can add its own constructors that take a record type the same way by decorating a classmethod with SubscriptableClassmethod.

A reader fixed to one record type can add FixedRecordType to its bases, and is then built without a subscript.

from typeline import FixedRecordType

class SiteReader(VcfLikeReader[Site], FixedRecordType):
    pass

with SiteReader.from_path(path) as reader:
    assert list(reader) == [Site("chr1", 100, None, {"DP": "10", "AF": "0.5"})]

More examples, from sample sheets to GFF3 and colored genomic features, are in tests/test_real_world_examples.py.

Development and Testing

See the contributing guide for more information.

Metadata

Release files for typeline 3.1.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 typeline 3.1.0
File Size Uploaded Provenance Actions
typeline-3.1.0.tar.gz 164.4 kB With provenance Details for typeline-3.1.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for typeline 3.1.0
File Actions
typeline-3.1.0-cp314-cp314t-win_amd64.whl CPython 3.14 CPython 3.14 free-threading Windows x86-64 Details for typeline-3.1.0-cp314-cp314t-win_amd64.whl
typeline-3.1.0-cp314-cp314t-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 Details for typeline-3.1.0-cp314-cp314t-musllinux_1_2_x86_64.whl
typeline-3.1.0-cp314-cp314t-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64 Details for typeline-3.1.0-cp314-cp314t-musllinux_1_2_aarch64.whl
typeline-3.1.0-cp314-cp314t-manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64 Details for typeline-3.1.0-cp314-cp314t-manylinux_2_28_aarch64.whl
typeline-3.1.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Details for typeline-3.1.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
typeline-3.1.0-cp314-cp314t-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 Details for typeline-3.1.0-cp314-cp314t-macosx_11_0_arm64.whl
typeline-3.1.0-cp314-cp314t-macosx_10_12_x86_64.whl CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64 Details for typeline-3.1.0-cp314-cp314t-macosx_10_12_x86_64.whl
typeline-3.1.0-cp311-abi3-win_amd64.whl CPython 3.11 abi3 Windows x86-64 Details for typeline-3.1.0-cp311-abi3-win_amd64.whl
typeline-3.1.0-cp311-abi3-musllinux_1_2_x86_64.whl CPython 3.11 abi3 Linux musl 1.2+ x86-64 Details for typeline-3.1.0-cp311-abi3-musllinux_1_2_x86_64.whl
typeline-3.1.0-cp311-abi3-musllinux_1_2_aarch64.whl CPython 3.11 abi3 Linux musl 1.2+ ARM64 Details for typeline-3.1.0-cp311-abi3-musllinux_1_2_aarch64.whl
typeline-3.1.0-cp311-abi3-manylinux_2_28_aarch64.whl CPython 3.11 abi3 Linux glibc 2.28+ ARM64 Details for typeline-3.1.0-cp311-abi3-manylinux_2_28_aarch64.whl
typeline-3.1.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.11 abi3 Linux glibc 2.17+ x86-64 Details for typeline-3.1.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
typeline-3.1.0-cp311-abi3-macosx_11_0_arm64.whl CPython 3.11 abi3 macOS 11.0+ ARM64 Details for typeline-3.1.0-cp311-abi3-macosx_11_0_arm64.whl
typeline-3.1.0-cp311-abi3-macosx_10_12_x86_64.whl CPython 3.11 abi3 macOS 10.12+ x86-64 Details for typeline-3.1.0-cp311-abi3-macosx_10_12_x86_64.whl

Total release size: 8.0 MB

Release files / typeline-3.1.0.tar.gz

Download URL typeline-3.1.0.tar.gz
Size 164.4 kB
Tags Source
SHA-256 checksum
How to use checksums
e65695fd84cd45ae888880f2f87de28249a776dce3fde0c3e747b6a246b1708c
BLAKE2b-256 checksum
How to use checksums
69440a333b21fe7447bbc3d952f6fb29ec2aa796f26dad93cefaf201ec8ab1a8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp314-cp314t-win_amd64.whl

Download URL typeline-3.1.0-cp314-cp314t-win_amd64.whl
Size 398.0 kB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
dbbda5e518237e2bdfc42b1c67f4094ec8c355f45d2797faf099db877c0aed3a
BLAKE2b-256 checksum
How to use checksums
3f061019ea68ac95675b4b47b6498aeac2b10852ac9794b39afcbb1646faac1d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp314-cp314t-musllinux_1_2_x86_64.whl

Download URL typeline-3.1.0-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 744.5 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
5c0e6675125a5937852998f18d15a0e240b7ede5f8ace12a9b5acdaa76ce0e3d
BLAKE2b-256 checksum
How to use checksums
8fb0ce9e7c38837264108765b34fc9e55a5513f350b50136416abd80551e779a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp314-cp314t-musllinux_1_2_aarch64.whl

Download URL typeline-3.1.0-cp314-cp314t-musllinux_1_2_aarch64.whl
Size 706.0 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
4d3649bd136736c2a04ce8eb0e6f733835db5b39af24899dfad4141a1572c92c
BLAKE2b-256 checksum
How to use checksums
43063f85a54965e8744468862ec15119e28cd7caf35168178f2ea2c32eae18bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp314-cp314t-manylinux_2_28_aarch64.whl

Download URL typeline-3.1.0-cp314-cp314t-manylinux_2_28_aarch64.whl
Size 526.8 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
0b3c75fef4ebec490773f69e5be7ae7f62d297e7b1c3be6deade770a6697c2fd
BLAKE2b-256 checksum
How to use checksums
7f447338cd3a4a0827d94877f8341bc115adb513d571d80738c94d03be1142bb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL typeline-3.1.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 529.9 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
1d3c704f8ed253e61679353c0706754d1ecf333ead7c60df675d60a15fbbce19
BLAKE2b-256 checksum
How to use checksums
c0d0414c193aad63e18bb40ddbd04852bae92e64c45c938d9d00e578a735cad9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp314-cp314t-macosx_11_0_arm64.whl

Download URL typeline-3.1.0-cp314-cp314t-macosx_11_0_arm64.whl
Size 489.3 kB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
64f5c776940b661fe161f67517a4944a72e1287ca1d1fceb8c15717a2d045edf
BLAKE2b-256 checksum
How to use checksums
ab22637ac7d133a694c63eba29229c314d85835dea90e913d5db4087e12ecd93
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp314-cp314t-macosx_10_12_x86_64.whl

Download URL typeline-3.1.0-cp314-cp314t-macosx_10_12_x86_64.whl
Size 498.7 kB
Tags CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
fd0a073856ec0bc156e57e53c99070da01fd4781d24963271c78fbfbdfd59e7b
BLAKE2b-256 checksum
How to use checksums
0c233e8045ed762f248affeb6543a99ab6708e5d96849355563acc006d77c1da
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp311-abi3-win_amd64.whl

Download URL typeline-3.1.0-cp311-abi3-win_amd64.whl
Size 408.8 kB
Tags CPython 3.11 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
08323c42e51c5d45a250c24d74572057ab47f5c1d1569ba378265a915a40fae6
BLAKE2b-256 checksum
How to use checksums
771dc46b1da4e45c0a3161d8a0c64d080986691c1a4c7ee5e920b75931a23257
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp311-abi3-musllinux_1_2_x86_64.whl

Download URL typeline-3.1.0-cp311-abi3-musllinux_1_2_x86_64.whl
Size 752.5 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
48fa26c527a936f5be99c7a239a7414fcbc97275d575073215de76af691e42d2
BLAKE2b-256 checksum
How to use checksums
ff94425d6d0fbdfc2077494475e59586ac46b371ae2dbb6f2d46591715f11e61
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp311-abi3-musllinux_1_2_aarch64.whl

Download URL typeline-3.1.0-cp311-abi3-musllinux_1_2_aarch64.whl
Size 713.2 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
0f822d96aabffb630abf6381255704c99b650a491af3b06f663d5d620b06d97c
BLAKE2b-256 checksum
How to use checksums
6f406c90561e249f6e7c7aea011cef0d4533183042223edc0cb16e491342839b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp311-abi3-manylinux_2_28_aarch64.whl

Download URL typeline-3.1.0-cp311-abi3-manylinux_2_28_aarch64.whl
Size 534.1 kB
Tags CPython 3.11 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
2831f9b950f287e17c4d25fac90cd7c88ce291d780e90f85c0b09610791b6f89
BLAKE2b-256 checksum
How to use checksums
5254ec4800a7e4d3170e77eac465a1695841ab80f8cc6ede8dde271ba23538b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL typeline-3.1.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 538.2 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
5673c7a8979a2b018687507efe5c5a99435ca7a12104d1640ffa2e99725e85c5
BLAKE2b-256 checksum
How to use checksums
10523775580050df0db447ceb4520bda13aafe77295bce15f5fb020d630bd253
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp311-abi3-macosx_11_0_arm64.whl

Download URL typeline-3.1.0-cp311-abi3-macosx_11_0_arm64.whl
Size 502.3 kB
Tags CPython 3.11 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
01568eba82c28b5d16c23d1ea0452be5216f989cd02a8ca7fa5dbc175303149b
BLAKE2b-256 checksum
How to use checksums
5cffd316c9088fb5a5ac31f0cae4912faf2c22e1d77c6572b17302f679be9aeb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / typeline-3.1.0-cp311-abi3-macosx_10_12_x86_64.whl

Download URL typeline-3.1.0-cp311-abi3-macosx_10_12_x86_64.whl
Size 499.2 kB
Tags CPython 3.11 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
e6ce20a5763df2c889863d5604fff84ef1f4289938cfd10c6cf754f4f03c81e9
BLAKE2b-256 checksum
How to use checksums
6a8b4cb40f02903aace6511042b85fdf3eec4f60e30e460549b4d9d33d1a2c8e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Security for typeline 3.1.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 15 files in this release have been uploaded with provenance metadata.

Select from 15 files

Attestation for typeline-3.1.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 24, 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.

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