Install xonsh with Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• xonsh
• xonsh-cat
• xonsh-uname
• xonsh-uptime

Project history

Anthony Scopatz's FAQ says the idea for xonsh came while reviewing the Bash chapter of Effective Computation in Physics and noticing how much shell practice depends on complex conventions for basic programming constructs. The FAQ frames xonsh as an answer to shells that do not fit the user's brain: Python supplies the familiar programming substrate, while xonsh adds enough shell behavior to make it usable as a daily command prompt.

The GitHub repository was created on 2015-01-21. The documentation and README describe xonsh as a superset of Python 3 with seamless integration of shell functionality and commands, implemented by parsing xonsh code into Python AST nodes and deciding between Python mode and subprocess mode when command-like input is ambiguous.

By 2016 xonsh had enough visibility for talks at PyCon and PyBay and coverage in developer publications. Later official talk listings include SciPy 2019 presentations, showing that the project found an audience among scientific Python, data, and systems users who wanted shell ergonomics without leaving the Python runtime.

Adoption history

Xonsh adoption has been strongest among Python-heavy developers, data scientists, and automation users who already value Python syntax and libraries. The project README explicitly demonstrates running subprocesses, mutating PATH, reading files with Python path literals, loading xontribs, and interop with tools such as Jupyter, Starship, and prompt integrations.

Its adoption pattern is less about replacing POSIX shell everywhere and more about creating a daily-driver shell for people who prefer Python's data structures, imports, and expression syntax. The official docs stress cross-platform support across Linux, macOS, Windows, BSD, Jupyter, Android, Raspberry Pi, WSL, Nix, AppImage, Flatpak, and other environments, which made it a natural package-manager item rather than a single-platform shell experiment.

How it is used

Typical use is interactive: set xonsh as a login or terminal shell, keep startup code in xonsh rc files, run normal external commands, and drop into Python expressions when shell text processing would be awkward. The tutorial emphasizes Python-mode versus subprocess-mode, environment variables as Python-accessible values, and explicit subprocess syntax for cases where ambiguity matters.

For automation, xonsh is useful when a task needs both shell pipelines and real Python data handling. Users commonly reach for it to glue command-line tools, JSON output, Python imports, prompt customization, and cross-platform path/environment logic without splitting the workflow between Bash and standalone Python scripts.

Why package nerds care

Xonsh is package-nerd significant because it makes the shell itself an application-runtime choice. Installing it changes not just one command but the language used at the prompt, the configuration files a user maintains, and the extension surface exposed through xontribs.

It is also a useful counterexample to the idea that every shell needs its own bespoke scripting language. Xonsh's design shows a different packaging story: ship a shell that borrows the host language's parser, AST, libraries, and package ecosystem, then add only the command-line affordances needed to make it feel native at a terminal.

Timeline

• 2015-01-21: The xonsh GitHub repository is created.
• 2016-06: Xonsh is presented at PyCon and covered by developer press.
• 2016-09: A PyBay talk appears in the official talks list.
• 2019-07: Xonsh is presented at SciPy by Anthony Scopatz and Gil Forsyth.
• 2026: The project documentation describes xonsh as a cross-platform Python-based shell with an ecosystem of xontrib extensions.

Related projects

• Python is the language substrate xonsh extends for shell use.
• IPython is a related Python command-line environment that xonsh explicitly contrasts with in its FAQ.
• fish, zsh, Bash, and Nushell are adjacent shells in the same usability and scripting-design space.
• xontrib packages are the extension layer for prompt integrations, completions, shell interop, and workflow-specific features.

Sources

• https://api.github.com/repos/xonsh/xonsh
• https://github.com/xonsh/xonsh
• https://raw.githubusercontent.com/xonsh/xonsh/main/docs/faq.rst
• https://raw.githubusercontent.com/xonsh/xonsh/main/docs/talks_and_articles.rst
• https://raw.githubusercontent.com/xonsh/xonsh/main/docs/tutorial.rst
• https://xon.sh/
• https://xon.sh/contents.html