Skip to main content

Python API

FOSU is in active development; its API may change without compatibility shims. Parsing returns eager objects and lists, detached from native memory. All records are read-only native objects with eager Python fields, declared and typed in _model.py. Attribute reads do not allocate numeric values. Lists remain ordinary mutable Python lists.

Install and use

Requires CPython 3.10+. Stable-ABI wheels target glibc and musl Linux on x86-64 and AArch64, plus macOS 11+ on Intel and Apple Silicon. One wheel per platform supports every compatible CPython version. Windows x86-64 is supported both natively and through the Linux x86-64 wheel under WSL.

python -m pip install fosu

Installing from a source checkout requires a C++20 compiler. An ordinary isolated pip install . provisions CMake and Ninja when needed; Unix Makefiles are also supported when Ninja is unavailable. --no-build-isolation makes the caller responsible for all build tools.

import fosu

beatmap = fosu.parse_file("map.osu")
for note in beatmap.hit_objects:
    if isinstance(note, fosu.Slider):
        print(note.time, note.length, note.control_points)

parse_file(path) accepts strings, bytes, and os.PathLike. parse(data) accepts buffer-protocol objects, including bytes, bytearray, memoryview, and arrays. Non-bytes buffers are copied to an immutable snapshot; encode text explicitly.

File failures raise OSError; other parse failures, including invalid options and inputs too large to allocate, raise ValueError. Native parsing releases the GIL; Python value construction holds it. Malformed records are skipped and counted in beatmap.stats.malformed_lines; success does not certify playability.

parse and parse_file allocate native memory for each call. To parse many maps, reuse a fosu.Parser, which keeps that memory until the parser is garbage-collected:

parser = fosu.Parser()
maps = [parser.parse_file(path) for path in paths]

Its parse and parse_file methods take the same arguments as the module functions. Results are detached, so later calls never change earlier results. One parser handles one call at a time; a concurrent call raises RuntimeError. Use one parser per thread.

Performance

FOSU commit f2c86ce (after 0.6.1), measured on 2026-10-04 using CPython 3.12.14 on an Intel Core i7-8700 under Linux/WSL2. All rows use the same 1,004 mutually accepted all-mode maps. Times include eager result construction and release; lower is better. Warm-file measurements include opening and reading page-cached files.

Python interface Resident bytes (µs/map) Warm file (µs/map)
FOSU AVX2, reused fosu.Parser 162.8 174.5
FOSU scalar, reused fosu.Parser 219.0 227.0
FOSU AVX2, fosu.parse per call 265.0 277.2
FOSU scalar, fosu.parse per call 324.4 334.2
OsuPyParser 1.0.7 Unsupported 4,418.9

A fosu.Parser keeps its memory between calls. The module functions create a new parser per call, which also reserves that memory and takes a page fault on the first write to each page; keep a Parser when parsing many maps.

Figures are the fastest of six complete passes per API, not fastest individual parses: every pass keeps the garbage collection its parsing causes. The parsers expose different models: OsuPyParser also performs derived-statistic work. See the comparison and measured variation for result contracts, or the feature-cost tables for slider geometry, gameplay, mods, and ARM measurements.

Section selection

listing = fosu.parse_file(
    "map.osu",
    sections=fosu.Sections.METADATA | fosu.Sections.DIFFICULTY,
)

Both entry points accept keyword-only sections, defaulting to Sections.ALL. Members are GENERAL, EDITOR, METADATA, DIFFICULTY, EVENTS, TIMING_POINTS, COLOURS, and HIT_OBJECTS. Combine them with |. Skipped sections retain defaults and empty lists; Sections(0) selects none. Unsupported mask bits are rejected.

Include GENERAL for mode-dependent difficulty rules (such as mania CircleSize) and EVENTS for break-dependent combo rules. Only selected sections contribute malformed-line counts.

Results and important distinctions

The model classes in _model.py define the fields and convenience methods. Shared fields use C++ names. Important Python-specific behavior:

  • hit_objects contains Circle, Slider, Spinner, or HoldNote, in stable timestamp order. Narrow the union with isinstance.
  • Times are milliseconds. Slider endpoints are 0 by default. Pass calculate_slider_end_times=True to parse or parse_file to calculate them using curve distance, timing and repeats. Do not use slider endpoints unless calculation was requested. Accessing the field never computes or caches anything. Other object types still have numeric endpoints. Omitted sections use their default settings. Hit samples and slider edge fields remain text.
  • Slider control_points includes the head position, unlike the native point range. curve_segments preserves modern segment boundaries and explicit B-spline degrees. slides=2 means forward and back.
  • tag_list and bookmark_list are parsed conveniences alongside the tags and bookmarks text fields.
  • IDs and preview time map the -1 sentinel to None.
  • Strings decode with UTF-8 surrogateescape, preserving undecodable bytes.
  • Inherited timing-point NaN beat lengths are preserved; consumers must not treat them as ordinary slider velocities.

Records support equality, repr, deepcopy, and pickle. They are not dataclasses: dataclasses.asdict and dataclasses.replace do not apply. Public record classes cannot be subclassed, and attributes cannot be assigned or deleted. Constructors accept positional or keyword arguments and retain the supplied values without runtime type validation. Parsed numeric fields are always eagerly converted to their documented Python types.

List contents can be changed without affecting the input or another parse result. Such changes do not recompute derived data. All records participate in cyclic garbage collection, including cycles consumers create through lists or values passed to constructors.

Pass calculate_slider_paths=True to retain each slider's path (otherwise None). fosu.slider_position_at(slider.path, progress) is a pure query over that polyline, with progress clamped to [0, 1]. Returned PathPoint coordinates are relative to the head; add the slider's x/y for playfield coordinates. Paths alone do not calculate end times. Requesting both reuses their distance. Native code exposes the same query and Beatmap.slider_paths, indexed by slider.

calculate_slider_events=True additionally populates slider.events with HEAD, TICK, REPEAT, LEGACY_LAST_TICK, and TAIL records in official generator order, grouped by slider-span traversal. This is not necessarily timestamp order: a legacy last tick may be timed before a late tick or the repeat beginning its final span. The legacy event is the effective historical tail judgement, not an additional score or combo event; the real TAIL and slider end_time remain unchanged. This option includes path and end-time calculation. Each record has time, span index/start time, path progress, and a position relative to the head. Native code exposes Beatmap.slider_events, indexed by slider. Without the option, events are empty. These are path events using the decoded slider's timing, not a converted ruleset's nested hitobjects: no samples or catch conversion. Expansion beyond 1,048,576 events per map fails the parse with ValueError rather than silently dropping events.

apply_stacking=True applies unmodded osu!standard stacking after parsing, including the pre-v6 algorithm. Hit-object x/y and absolute slider control points are adjusted before returning. obj.raw_position() subtracts the stacking offset from the current x/y, or returns x/y when stacking is absent. It can have small floating-point rounding differences. Coordinates are floats in both interfaces, including when stacking is disabled. Each object also retains stack_height and stack_offset in its Stacking value for inspection; do not add the offset again. Relative path/event positions remain unchanged: add them to the adjusted head. It includes path and end-time calculation, but not events. Native results use Beatmap.stacking, indexed by hit object. Other modes are unchanged; Python stacking is None when not calculated. Include GENERAL, DIFFICULTY, TIMING_POINTS and HIT_OBJECTS when selecting sections for meaningful results.

mods= accepts combined Mods values. EZ and HR adjust difficulty settings for osu!standard and osu!taiko; HR also reflects standard hit objects and slider control points vertically. EZ/HR require GENERAL and DIFFICULTY in sections. They are not yet supported for osu!catch or osu!mania because those modes require converted fruit offsets or resolved hit windows; support is planned. DT, NIGHTCORE, and HT support every mode and divide gameplay timeline values by 1.5, 1.5, and 0.75 respectively. This includes hit objects, calculated slider events, timing-point offsets and uninherited beat lengths, and breaks. General and Editor timestamp metadata remains in source-map time.

See compatibility for supported behavior and limitations; there is no ruleset conversion.

CPU selection

fosu.backend reports "avx2", "neon", or "scalar". Set FOSU_BACKEND=auto|scalar|avx2|neon before importing to select an engine. Unsupported explicit requests raise ImportError; selection stays fixed for the loaded extension. See development checks.

Metadata

Release files for fosu 0.6.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 fosu 0.6.1
File Size Uploaded Provenance Actions
fosu-0.6.1.tar.gz 249.1 kB With provenance Details for fosu-0.6.1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for fosu 0.6.1
File Actions
fosu-0.6.1-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details for fosu-0.6.1-cp310-abi3-win_amd64.whl
fosu-0.6.1-cp310-abi3-musllinux_1_2_x86_64.whl CPython 3.10 abi3 Linux musl 1.2+ x86-64 Details for fosu-0.6.1-cp310-abi3-musllinux_1_2_x86_64.whl
fosu-0.6.1-cp310-abi3-musllinux_1_2_aarch64.whl CPython 3.10 abi3 Linux musl 1.2+ ARM64 Details for fosu-0.6.1-cp310-abi3-musllinux_1_2_aarch64.whl
fosu-0.6.1-cp310-abi3-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 abi3 Linux glibc 2.28+ x86-64, Linux glibc 2.26+ x86-64 Details for fosu-0.6.1-cp310-abi3-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl
fosu-0.6.1-cp310-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 abi3 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for fosu-0.6.1-cp310-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
fosu-0.6.1-cp310-abi3-macosx_11_0_x86_64.whl CPython 3.10 abi3 macOS 11.0+ x86-64 Details for fosu-0.6.1-cp310-abi3-macosx_11_0_x86_64.whl
fosu-0.6.1-cp310-abi3-macosx_11_0_arm64.whl CPython 3.10 abi3 macOS 11.0+ ARM64 Details for fosu-0.6.1-cp310-abi3-macosx_11_0_arm64.whl

Total release size: 2.3 MB

Release files / fosu-0.6.1.tar.gz

Download URL fosu-0.6.1.tar.gz
Size 249.1 kB
Tags Source
SHA-256 checksum
How to use checksums
c0bb7f8b92f6f9ee6f58ca2dc4d0675bdca758d5154f71437690edc4833788b5
BLAKE2b-256 checksum
How to use checksums
b1aab47351960627ada5bed1d5cfda64d15139a59240308df99cd19dd168b39f
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 4, 2026.

Transparency log

Release files / fosu-0.6.1-cp310-abi3-win_amd64.whl

Download URL fosu-0.6.1-cp310-abi3-win_amd64.whl
Size 342.9 kB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
2ee7dc04f9fe9e4116b03abe71c4c3a6a725af859a68be8ccea55df032d13f7c
BLAKE2b-256 checksum
How to use checksums
6515785555871cb488a21c92a0187a43e2c73408c4899c1cf53fe33a969a5f9d
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 4, 2026.

Transparency log

Release files / fosu-0.6.1-cp310-abi3-musllinux_1_2_x86_64.whl

Download URL fosu-0.6.1-cp310-abi3-musllinux_1_2_x86_64.whl
Size 330.1 kB
Tags CPython 3.10 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
240e6709ea95444740d690383d21a9fcba48297715eeb0d1f7b6d4aa7f263cec
BLAKE2b-256 checksum
How to use checksums
892f4c02de5732bc73092d06b9d5d0fabe9dec6841f9adf78c250d70ded6cd0a
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 4, 2026.

Transparency log

Release files / fosu-0.6.1-cp310-abi3-musllinux_1_2_aarch64.whl

Download URL fosu-0.6.1-cp310-abi3-musllinux_1_2_aarch64.whl
Size 352.1 kB
Tags CPython 3.10 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
57073af6f432701af4a17482c253cdf44c8bbbe33990358507800efe3bb660e2
BLAKE2b-256 checksum
How to use checksums
b1e27438571e4637df61745eacc554482b71cd80e90df8ca75357312b569bc93
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 4, 2026.

Transparency log

Release files / fosu-0.6.1-cp310-abi3-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl

Download URL fosu-0.6.1-cp310-abi3-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl
Size 331.3 kB
Tags CPython 3.10 Linux glibc 2.26+ x86-64 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
122c2a046eb4f0e0229c66012e95e54c3fd96e8fb60309ca7e0ac587ccf0de67
BLAKE2b-256 checksum
How to use checksums
9a820655916a539adf7bacc51b278b357fdc63e439af5935f1fa356e7226bf23
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 4, 2026.

Transparency log

Release files / fosu-0.6.1-cp310-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL fosu-0.6.1-cp310-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 352.2 kB
Tags CPython 3.10 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
e94fafdfa72966ed0016bbc693a7b46b85873a612d76a6deaf549213545247f0
BLAKE2b-256 checksum
How to use checksums
540b2683cc22575a6b09e2cacd70a3213a3b07b3dbbbedae8dde23032bb60ae0
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 4, 2026.

Transparency log

Release files / fosu-0.6.1-cp310-abi3-macosx_11_0_x86_64.whl

Download URL fosu-0.6.1-cp310-abi3-macosx_11_0_x86_64.whl
Size 157.2 kB
Tags CPython 3.10 abi3 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
a75e727864618c5d6b58eb1c75765106f1c04b1e25c16b6a8e6917f9fa0d9320
BLAKE2b-256 checksum
How to use checksums
cbb40c641c285ead1b9b72e7023248b2486c668044a2b072d71e71cb2891fc3b
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 4, 2026.

Transparency log

Release files / fosu-0.6.1-cp310-abi3-macosx_11_0_arm64.whl

Download URL fosu-0.6.1-cp310-abi3-macosx_11_0_arm64.whl
Size 146.7 kB
Tags CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
81919c0e65cced3477f718e294469421c389dddf002b6de1091a21c36127db6c
BLAKE2b-256 checksum
How to use checksums
b1393c9da5736c31d6915eb28f2f5f51af56893babb7e96bc58f57b4886547ea
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 4, 2026.

Transparency log

Security for fosu 0.6.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 8 files in this release have been uploaded with provenance metadata.

Select from 8 files

Attestation for fosu-0.6.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 4, 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