pydocstring

A zero-dependency Rust parser for Python docstrings (Google / NumPy style).

Produces a unified syntax tree with byte-precise source locations on every token — designed as infrastructure for linters and formatters.

Python bindings are also available as pydocstring-rs.

Features

• Full syntax tree — builds a complete AST, not just extracted fields; traverse it with the built-in Visitor + walk_tree
• Typed nodes per style — style-specific accessors like GoogleArg, NumPyParameter with full type safety
• Byte-precise source locations — every token carries its exact byte range for pinpoint diagnostics
• Zero dependencies — pure Rust, no external crates, no regex
• Error-resilient — never panics; malformed input still yields a best-effort tree
• Style auto-detection — hand it a docstring, get back Style::Google, Style::NumPy, or Style::Plain
• Pattern matching & rewriting — find and replace constructs with $NAME / $$$NAME patterns, substituting byte-exact captured content so everything you don't rewrite is preserved

Installation

[dependencies]
pydocstring = "0.3.1"

Usage

Parsing

Parse with auto-detection and traverse the style-independent views — one code path for every docstring style:

use pydocstring::model::SectionKind;
use pydocstring::parse::{parse, Document};

let input = "Summary.\n\nArgs:\n    x (int): The value.\n    y (int): Another value.";
let parsed = parse(input);
let doc = Document::new(&parsed);

println!("{}", doc.summary().unwrap().text());

for section in doc.sections() {
    if section.kind() == SectionKind::Parameters {
        for entry in section.entries() {
            println!("{}: {}",
                entry.name().map(|n| n.text()).unwrap_or(""),
                entry.type_annotation().map(|t| t.text()).unwrap_or(""));
        }
    }
}

When you know the style (or want to force it), the per-style parsers expose style-specific typed wrappers:

use pydocstring::parse::google::{parse_google, GoogleDocstring, GoogleSectionKind};

let input = "Summary.\n\nArgs:\n    x (int): The value.\n    y (int): Another value.";
let result = parse_google(input);
let doc = GoogleDocstring::cast(&result, result.root()).unwrap();

for section in doc.sections() {
    if section.section_kind() == GoogleSectionKind::Args {
        for arg in section.args() {
            println!("{}: {}",
                arg.name().text(),
                arg.type_annotation().map(|t| t.text()).unwrap_or(""));
        }
    }
}

NumPy style works the same way — use parse_numpy / NumPyDocstring instead.

Style Auto-Detection

use pydocstring::parse::{detect_style, Style};

assert_eq!(detect_style("Summary.\n\nArgs:\n    x: Desc."), Style::Google);
assert_eq!(detect_style("Summary.\n\nParameters\n----------\nx : int"), Style::NumPy);
assert_eq!(detect_style("Just a summary."), Style::Plain);

Style::Plain covers docstrings with no recognised section markers: summary-only, summary + extended summary, and unrecognised styles such as Sphinx.

Unified Auto-Detecting Parser

Use parse() to let the library detect the style and parse in one step:

use pydocstring::parse::{parse, Style};
use pydocstring::syntax::SyntaxKind;

let result = parse("Summary.\n\nArgs:\n    x: Desc.");
assert_eq!(result.root().kind(), SyntaxKind::DOCUMENT);
assert_eq!(result.style(), Style::Google);

let result = parse("Just a summary.");
assert_eq!(result.style(), Style::Plain);

Source Locations

Every token carries byte offsets for precise diagnostics:

use pydocstring::parse::google::{parse_google, GoogleDocstring, GoogleSectionKind};

let result = parse_google("Summary.\n\nArgs:\n    x (int): The value.");
let doc = GoogleDocstring::cast(&result, result.root()).unwrap();

for section in doc.sections() {
    if section.section_kind() == GoogleSectionKind::Args {
        for arg in section.args() {
            let name = arg.name();
            println!("'{}' at byte {}..{}",
                name.text(), name.range().start(), name.range().end());
        }
    }
}

Syntax Tree

The parse result is a tree of SyntaxNode (branches) and SyntaxToken (leaves), each tagged with a SyntaxKind. Use pretty_print() to visualize:

use pydocstring::parse::google::parse_google;

let result = parse_google("Summary.\n\nArgs:\n    x (int): The value.");
println!("{}", result.pretty_print());

DOCUMENT@0..42 {
  SUMMARY: "Summary."@0..8
  SECTION@10..42 {
    SECTION_HEADER@10..15 {
      NAME: "Args"@10..14
      COLON: ":"@14..15
    }
    ENTRY@20..42 {
      NAME: "x"@20..21
      OPEN_BRACKET: "("@22..23
      TYPE: "int"@23..26
      CLOSE_BRACKET: ")"@26..27
      COLON: ":"@27..28
      DESCRIPTION: "The value."@29..39
    }
  }
}

Visitor Pattern

Walk the tree with the Visitor trait for style-agnostic analysis:

use pydocstring::syntax::{Visitor, walk_tree, SyntaxToken, SyntaxKind};
use pydocstring::parse::google::parse_google;

struct NameCollector<'a> {
    source: &'a str,
    names: Vec<String>,
}

impl Visitor for NameCollector<'_> {
    fn visit_token(&mut self, token: &SyntaxToken) {
        if token.kind() == SyntaxKind::NAME {
            self.names.push(token.text(self.source).to_string());
        }
    }
}

let result = parse_google("Summary.\n\nArgs:\n    x: Desc.\n    y: Desc.");
let mut collector = NameCollector { source: result.source(), names: vec![] };
walk_tree(result.root(), &mut collector);
assert_eq!(collector.names, vec!["Args", "x", "y"]);

Style-Independent Model (IR)

Convert any parsed docstring into a style-independent intermediate representation for analysis or transformation:

use pydocstring::parse::google::{parse_google, to_model::to_model};

let parsed = parse_google("Summary.\n\nArgs:\n    x (int): The value.\n");
let doc = to_model(&parsed).unwrap();

assert_eq!(doc.summary.as_deref(), Some("Summary."));
for section in &doc.sections {
    if let pydocstring::model::Section::Parameters(params) = section {
        assert_eq!(params[0].names, vec!["x"]);
        assert_eq!(params[0].type_annotation.as_deref(), Some("int"));
    }
}

Emitting (Code Generation)

Re-emit a Docstring model in any style — useful for style conversion or formatting. Google, NumPy, and Sphinx (reStructuredText) output are supported:

use pydocstring::model::{Docstring, Section, Parameter};
use pydocstring::emit::EmitOptions;
use pydocstring::emit::google::emit_google;
use pydocstring::emit::numpy::emit_numpy;
use pydocstring::emit::sphinx::emit_sphinx;

let doc = Docstring {
    summary: Some("Brief summary.".into()),
    sections: vec![Section::Parameters(vec![Parameter {
        names: vec!["x".into()],
        type_annotation: Some("int".into()),
        description: Some("The value.".into()),
        is_optional: false,
        default_value: None,
    }])],
    ..Default::default()
};

let options = EmitOptions::default();
let google = emit_google(&doc, &options);
assert!(google.contains("Args:"));

let numpy = emit_numpy(&doc, &options);
assert!(numpy.contains("Parameters\n----------"));

let sphinx = emit_sphinx(&doc, &options);
assert!(sphinx.contains(":param x:"));
assert!(sphinx.contains(":type x: int"));

// Indent the output for embedding in a Python file:
let indented = emit_google(&doc, &EmitOptions::default().with_base_indent(4));
assert!(indented.starts_with("    Brief summary."));

Note: Sphinx support is emit-only. detect_style reports Sphinx docstrings as Style::Plain, so parsing them yields a summary/extended-summary only.

Combine parsing and emitting to convert between styles:

use pydocstring::parse::google::{parse_google, to_model::to_model};
use pydocstring::emit::EmitOptions;
use pydocstring::emit::numpy::emit_numpy;

let parsed = parse_google("Summary.\n\nArgs:\n    x (int): The value.\n");
let doc = to_model(&parsed).unwrap();
let numpy_text = emit_numpy(&doc, &EmitOptions::default());
assert!(numpy_text.contains("Parameters\n----------"));

Pattern Matching & Rewriting

Find constructs with a $NAME / $$$NAME pattern and rewrite them with a template. Captured metavariables substitute the original source bytes, so everything you don't explicitly rewrite is preserved byte-for-byte — the issue The issue #26 use case of annotating one entry without reflowing the rest:

use pydocstring::parse::{parse, Style};
use pydocstring::pattern::Pattern;

let src = "Summary.\n\nArgs:\n    x (int): The value.\n    y (str): Kept.\n";
let parsed = parse(src);
let pattern = Pattern::new(Style::Google, "$NAME (int): $DESC").unwrap();

let out = parsed.replace(&pattern, "$NAME (int): $DESC (deprecated)").unwrap();
assert_eq!(
    out,
    "Summary.\n\nArgs:\n    x (int): The value. (deprecated)\n    y (str): Kept.\n",
);

In Python the same lives on the docstring wrappers as doc.replace(pattern, template) and doc.findall(pattern):

import pydocstring

doc = pydocstring.parse_google("Summary.\n\nArgs:\n    x (int): The value.\n")
new_src = doc.replace("$NAME ($TYPE): $DESC", "$NAME ($TYPE): $DESC (deprecated)")
for m in doc.findall("$NAME ($TYPE): $DESC"):
    print(m.capture("NAME").text, m.capture("TYPE").text)

Supported Sections

Both styles support the following section categories. Typed accessor methods are available on each style's section node.

Root-level accessors: summary(), extended_summary(), and deprecation() (Google and NumPy). PlainDocstring exposes only summary() and extended_summary().

Development

Common tasks are wrapped in a justfile — run just to list them:

just            # list all recipes
just lint       # cargo clippy (warnings as errors)
just test       # Rust test suite
just py-test    # build the Python extension (uv + maturin) and run pytest
just ci         # everything CI runs: fmt-check, lint, test, py-test

Or invoke cargo directly:

cargo build
cargo test
cargo run --example parse_auto
cargo run --example parse_google
cargo run --example parse_numpy