# Install docutils with Homebrew, Nix, zypper

Text processing system for reStructuredText. Version 0.23 via Homebrew; verified 2026-05-28. Also installable with nix: nix profile install nixpkgs#docutils.

## Install

```sh
sudo av install brew:docutils
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install docutils
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#docutils
```

  Evidence: nixpkgs package indexes: docutils from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix

- zypper (92%):

```sh
sudo zypper install python313-docutils
```

  Evidence: openSUSE Tumbleweed package metadata: python313-docutils from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

## Package facts

- **Package key:** brew:docutils
- **Package manager:** Homebrew
- **Version:** 0.23
- **Source summary:** Text processing system for reStructuredText
- **Homepage:** <https://docutils.sourceforge.io>
- **Last updated:** 2026-05-28T18:47:22Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- docutils (alias)
- rst2html (alias)
- rst2html4 (alias)
- rst2html5 (alias)
- rst2latex (alias)
- rst2man (alias)
- rst2odt (alias)
- rst2pseudoxml (alias)
- rst2s5 (alias)
- rst2xetex (alias)
- rst2xml (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.23
## Project history and usage

Docutils is the long-running Python documentation-processing system behind reStructuredText. It provides a Python library, parsers, writers, transforms, and front-end commands such as `rst2html`, `rst2latex`, `rst2man`, and `rst2xml`.

### Project history

The project's roots are in the Python documentation community. reStructuredText was designed by David Goodger as a revision and reinterpretation of StructuredText and Setext, with goals of readable plaintext markup, unambiguous parsing, and conversion into useful structured formats.

Docutils grew out of Python Doc-SIG discussions around docstring processing. Goodger's history notes StructuredText's 1996 origins, his late-1999 encounter with it, a November 2000 first draft of a revised specification, a June 2001 project web site and first release, and the 2002 merger of the reStructuredText and Docstring Processing System projects into Docutils.

### Adoption history

Docutils became the reference implementation for reStructuredText and a foundation for Python documentation tooling. The FAQ describes support for standalone files, PEPs, Python docstrings, and client code such as Sphinx extensions, while Homebrew and PyPI packaging keep the command-line tools widely available.

### How it is used

Users run front-end tools to convert reStructuredText to HTML, LaTeX, man pages, ODT, XML, pseudoxml, and other formats, or call the `docutils` Python package as a library. Configuration can come from system, local, or user-level docutils config files.

### Why package nerds care

Docutils is package-nerd significant because it is infrastructure disguised as a text converter. It links Python docstring conventions, PEP publishing, Sphinx-era documentation, command-line document conversion, and a decades-long release history into one small but foundational package.

### Timeline

- 1996: StructuredText first released in the Zope ecosystem.
- 1999: David Goodger discovered StructuredText while looking for Python module documentation tooling.
- 2000: First reStructuredText draft posted to Python Doc-SIG.
- 2001: Project web site and first release rolled out.
- 2002: reStructuredText and Docstring Processing System projects merged and renamed Docutils.
- 2026: Docutils 0.23 listed in release notes and packaged by Homebrew.

### Related projects

- Docutils is related to StructuredText, Setext, Python PEP tooling, Sphinx, and the wider Python documentation ecosystem. Its FAQ explicitly points to Sphinx as client code using reStructuredText for Python auto-documentation.

### Sources

- <https://docutils.sourceforge.io/FAQ.html>
- <https://docutils.sourceforge.io/docs/ref/rst/introduction.html>
- <https://docutils.sourceforge.io/docs/ref/rst/history.html>
- <https://docutils.sourceforge.io/RELEASE-NOTES.html>
- <https://sourceforge.net/p/docutils/code/HEAD/tree>
- <https://formulae.brew.sh/api/formula/docutils.json>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: /etc/docutils.conf, ./docutils.conf, ~/.docutils
## Other Package-Manager Records

- Nix - docutils: normalized package name match | nixpkgs package indexes: docutils from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix
- zypper - python313-docutils - 0.23-1.1: normalized package name match | openSUSE Tumbleweed package metadata: python313-docutils from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Python Documentation Utilities | https://pypi.python.org/pypi/docutils/
- Nix - rst2html5: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/rs/rst2html5/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/docutils.yml](https://github.com/mxcl/pkgdb/blob/main/combined/docutils.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
