Install jupytext with Homebrew, apt

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• jupytext
• jupytext-config

Project history

Jupytext was created by Marc Wouts and the GitHub repository was created on 2018-06-15. The project appeared during a period when Jupyter notebooks were already widely used but their JSON format made code review, merge conflict handling, and text-editor workflows awkward.

By early 2019, Jupytext 1.0 had established the paired-notebook workflow: users could keep a notebook synchronized with a `.py`, `.md`, `.Rmd`, or similar text representation. The official changelog records the addition of Jupyter Notebook and JupyterLab extensions and a growing command-line interface around paired paths and conversion.

Adoption history

Jupytext adoption has followed the pain points of notebook-heavy teams: clean Git diffs, less noisy review, editable scripts, and reproducible notebooks without storing outputs. The official FAQ recommends versioning only the text representation when outputs are not needed, while regenerating the `.ipynb` file locally.

The package metadata in this batch shows Jupytext in Homebrew and Debian-family packaging, and the official repository metadata showed more than 7,000 GitHub stars on 2026-07-01. Its adoption is especially visible in research, education, and data-science repositories that want notebooks and conventional source control at the same time.

How it is used

Jupytext is used from the command line with `jupytext`, from JupyterLab and Notebook menus, and through configuration files such as `jupytext.toml` or `pyproject.toml`. Typical workflows pair an `.ipynb` file with a percent-format Python script or Markdown file, then commit the text file for readable diffs.

It is also used as a bridge between notebook interfaces and IDEs: edit the text representation in an editor, open it as a notebook, or synchronize it with an `.ipynb` file when rich outputs are needed.

Why package nerds care

Jupytext is a classic package-nerd fix for a format mismatch. It does not replace notebooks; it makes them behave like source files when package managers, Git, code review, pre-commit hooks, and IDEs expect text.

Its importance comes from being small but ecosystem-shaped: it touches Jupyter server extensions, lab extensions, CLI conversion, file format conventions, and project configuration without forcing users to abandon the notebook UI.

Timeline

• 2018-06-15: The Jupytext GitHub repository is created.
• 2019-02-19: Marc Wouts publishes a Jupytext 1.0 highlights post.
• 2019-02-23: PyPI records the Jupytext 1.0.1 release candidate.
• 2022-11-11: Project Jupyter documentation describes Jupytext as a common way to save notebooks as Markdown for version control.
• 2024-02-16: The Jupyter Blog announces the return of the Jupytext menu for JupyterLab-era workflows.
• 2026-06-21: Jupytext 1.19.4 is published on GitHub.

Related projects

• JupyterLab and Jupyter Notebook are the notebook interfaces Jupytext integrates with.
• Git is the version-control system whose text-diff model motivates many Jupytext workflows.
• MyST Markdown and R Markdown are related plain-text notebook/document formats supported by the Jupytext ecosystem.
• nbconvert and notebook execution tools often appear near Jupytext in reproducible notebook pipelines.

Sources

• https://api.github.com/repos/mwouts/jupytext
• https://blog.jupyter.org/the-jupytext-menu-is-back-3e6212e8c090
• https://github.com/mwouts/jupytext
• https://github.com/mwouts/jupytext/releases
• https://jupytext.org/
• https://jupytext.org/reference/faq/
• https://jupytext.readthedocs.io/en/latest/changelog.html
• https://pypi.org/project/jupytext/1.0.1rc0/