Installer ipython avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• ipython
• ipython3

Historique du projet

The official IPython history says Fernando Perez started IPython in 2001 while a graduate student at the University of Colorado, Boulder. It grew from three projects: Perez's ipython, Janko Hauser's IPP, and Nathan Gray's LazyPython.

Perez's stated goal was to combine shell-like features, IDL/Matlab-style numerical work, Mathematica-like prompt and output history, and strong object introspection into a unified Python environment. That origin explains why IPython became both a programmer convenience tool and a scientific-computing foundation.

IPython later became the human-facing terminal shell part of a larger interactive-computing ecosystem. The Jupyter split moved notebooks, kernels, and language-agnostic protocols into Jupyter projects, while IPython continued as the Python terminal shell, kernel implementation lineage, and library of interactive features.

The long 8.x release notes show ongoing adaptation to Python version changes, prompt-toolkit behavior, debugger behavior, magics, rich display, and even experimental LLM completion hooks, while preserving the central command-line shell identity.

Historique d'adoption

IPython was adopted heavily in scientific Python because it made exploratory programming feel closer to mathematical systems while remaining ordinary Python. It became a common dependency or companion for NumPy, SciPy, matplotlib, notebooks, teaching environments, and data-analysis workflows.

Package managers matter to IPython's spread: it is shipped by Homebrew and major Linux distributions, while Python users also install it through Python packaging tools. That dual identity makes it both a system package and a Python ecosystem package.

Modes d'utilisation

Users run the ipython command for an enhanced REPL with tab completion, introspection, command history, magics, shell escapes, debugging helpers, rich tracebacks, and custom display hooks. Configuration lives under IPython profiles, including files such as ipython_config.py and ipython_config.json.

IPython is also used indirectly by tools that embed interactive shells, expose kernels, or rely on IPython display and completion behavior. Its API surface is larger than the visible command because interactive Python became a platform for other developer tools.

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

IPython is package-nerd significant because it is a package that changed user expectations for a language runtime's shell without replacing the language. Its dependency graph, configuration files, terminal integration, and split history with Jupyter make it more than just a binary named ipython.

It is also a case study in ecosystem boundary-setting: notebooks, kernels, and protocols became Jupyter projects, while IPython kept the Python-specific shell and interactive machinery.

Chronologie

• 2001: Fernando Perez starts IPython at the University of Colorado, Boulder.
• 2001: IPython combines ideas from ipython, IPP, and LazyPython.
• 2014: The broader IPython notebook ecosystem moves toward the Jupyter project identity.
• 2015: IPython 4 era aligns with the Jupyter split, leaving IPython focused on Python-specific interactive pieces.
• 2022: The 8.x series begins for modern Python versions and prompt-toolkit based terminal workflows.
• 2025: 8.x release notes document Python 3.13 compatibility and experimental LLM completion work.

Related projects

• IPython is related to Jupyter, IPykernel, prompt_toolkit, jedi, traitlets, NumPy, SciPy, matplotlib, IPP, LazyPython, and Python's standard interactive interpreter.

Sources

• https://formulae.brew.sh/formula/ipython
• https://github.com/ipython/ipython
• https://ipython.org/documentation.html
• https://ipython.readthedocs.io/en/stable
• https://ipython.readthedocs.io/en/stable/about/history.html
• https://raw.githubusercontent.com/ipython/ipython/main/docs/source/whatsnew/version8.rst