Installer austin avec Homebrew, apt, scoop, winget

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• austin

Historique du projet

The public GitHub repository was created in September 2018 and describes Austin as a pure-C sampler that reads the CPython interpreter's memory to recover executing frames and threads. Its own README emphasizes zero instrumentation, low overhead, wall-time and memory profiling, and multiprocess support.

Austin has tracked CPython internals over time. Recent official releases added CPython 3.12, 3.13, and 3.14 support, dropped older interpreter support, improved container and interpreter detection, and moved the default binary output format to MOJO in the 4.0.0 series.

Historique d'adoption

Austin became more than a GitHub-only tool early in its life: the README notes acceptance into Debian repositories on March 30, 2019, and documents installation through PyPI, Snap, Debian/apt, Homebrew, Chocolatey, Scoop, and Conda Forge. Homebrew's formula currently packages Austin 4.0.0 from the upstream GitHub release tarball.

The repository metadata shows thousands of GitHub stars and ongoing releases, while Homebrew analytics in the formula API show modest but real package-manager use. For a native Python profiler, that breadth of packaging is part of the story: users can install it as a system command instead of treating it as a Python library dependency.

Modes d'utilisation

Austin is typically used by running `austin` around or against a Python workload, then feeding its collapsed-stack or binary output into visualization tools. The README explicitly calls out use with the Austin VS Code extension, Brendan Gregg's FlameGraph tools, and Speedscope conversion through the related Austin Python tooling.

Its value is operational: no source-code instrumentation, low tracee impact, support for memory mode, and enough portability to cover Linux, macOS, and Windows packaging paths.

Pourquoi les passionnés de paquets s'y intéressent

Package nerds care about Austin because it is a native executable wrapped by language and OS package managers at once. It is distributed as `austin-dist` on PyPI, as a Homebrew formula, as OS packages, and as release binaries, while still depending on CPython implementation details that require active maintenance.

It is also a good example of a CLI whose package identity is not quite the same as its library ecosystem identity: the Homebrew formula is `austin`, the PyPI install is `austin-dist`, and the output is meant to be composed with classic Unix-style profiler visualization tools.

Chronologie

• 2018: Public GitHub repository created.
• 2019: Austin accepted into the official Debian repositories.
• 2023: Austin 3.6.0 added CPython 3.12 support and dropped Python 2 and older CPython 3 releases.
• 2024: Austin 3.7.0 added CPython 3.13 support and improved container support.
• 2025: Austin 4.0.0 added CPython 3.14 support and made MOJO binary output the default.

Related projects

• Austin commonly appears alongside FlameGraph, Speedscope, the Austin VS Code extension, and the `austin-python` tooling used for conversion and higher-level profiler workflows.

Sources

• https://api.github.com/repos/P403n1x87/austin
• https://formulae.brew.sh/api/formula/austin.json
• https://github.com/P403n1x87/austin#readme
• https://github.com/P403n1x87/austin/releases
• source_facts.package-manager