Files
Lee DogeonandClaude Sonnet 5 44dcd1de2d ci: add pyperformance benchmarking scripts and workflow (#8691)
* Add script to run upstream pyperformance against RustPython

pyperformance can't be installed as-is on RustPython since pyperf hard-depends
on psutil, a C extension RustPython cannot build or load (no CPython C-API /
extension-module support). Since pyperf already disables psutil usage on
interpreters reporting Py_GIL_DISABLED=1 (which RustPython does, having no
GIL), a functionality-free pure-Python psutil stub is enough to satisfy pip's
dependency resolution and unblock any pure-Python benchmark.

scripts/pyperformance/run_all.py drives pyperformance (under a host CPython
venv) with RustPython as the --python target, installs the stub via
PIP_FIND_LINKS + --inherit-environ, and catalogs pass/fail/timeout per
benchmark with an automatic failure classifier (C-extension build blocked vs.
a genuine exception raised by the benchmark itself).

Assisted-by: Claude Code:claude-sonnet-5

* pyperformance: support targeting any Python and comparing catalogs

Generalize run_all.py from a RustPython-only runner to a --python/--label
pair, so the same script can catalog a real CPython (with --no-psutil-stub,
since it has a genuine psutil) alongside RustPython. Each label gets its own
results/<label>/ subdirectory.

Add compare.py, which loads two labels' catalogs and writes a per-benchmark
Markdown table with both targets' status/mean and the candidate/baseline
time ratio, plus the median slowdown across benchmarks both targets passed.

Assisted-by: Claude Code:claude-sonnet-5

* ci: compare base, head and CPython with pyperformance on one runner

A ratio between two pyperformance runs measured on different machines can
move further than the change under review did, so a PR's numbers are only
worth reading when base, head and CPython were measured back to back on the
same runner. This adds a job that does exactly that -- two release builds
kept side by side with the stdlib of their own commit, then three runs with
nothing in between -- and posts the table as a PR comment.

`pr_diff.py` renders the three catalogs `run_all.py` writes: per benchmark
the CPython time, both RustPython times, both ratios against CPython, and
the head/base change, with anything under 3% shown as `~` because a shared
runner is not quiet enough to say more.

The comment is handed to a `workflow_run` companion the same way
`codspeed-comment.yaml` does it, since a `pull_request` run from a fork gets
a read-only token however the workflow is configured.

The job is opt-in behind a `run:pyperformance` label: it runs 28 benchmarks
three times over and costs well over an hour, which most PRs do not need.

`run_all.py` now forwards RUSTPYTHONPATH through pyperf, which a binary
copied away from its checkout needs in order to find the stdlib at all; the
two names go in one comma-separated `--inherit-environ`, because repeating
the flag keeps only the last.

Assisted-by: Claude Code:claude-fable-5-1

* ci: comment from the pyperformance run itself when the PR allows it

The `workflow_run` companion only starts firing once it is on the default
branch, so a pull request that introduces it -- this one -- would upload the
table and never show it. A pull request opened from this repo carries a
token that may write comments, so post it from the run that measured it and
leave the companion to the forks that genuinely cannot.

Both paths upsert on the same marker, so a fork PR that reaches the
companion after this step was skipped still lands one comment.

Assisted-by: Claude Code:claude-fable-5-1

* ci: address zizmor findings and fall back to head vs. CPython

- Pin `actions/github-script` to the commit the rest of the repo pins it to;
  the hash carried over from an in-flight branch pointed elsewhere than the
  `v9.0.0` comment claimed (ref-version-mismatch).
- Read the PR number, the CPython path and version, and the two commit shas
  from `env` rather than expanding them into the shell (template-injection).
- Record the `workflow_run` trigger in `.github/zizmor.yml` next to the
  existing `pull_request_target` entry, with the same justification: the
  workflow reads one artifact and writes a comment, and never checks out or
  runs pull request code (dangerous-triggers).

Building or measuring the base commit is now non-fatal, and `pr_diff.py`
renders head against CPython alone when the base column has nothing in it --
a base that will not build should still leave a usable table rather than
failing the job. The time and ratio columns are also named apart, since
`| base | head | base | head |` gave no clue which pair was which.

Assisted-by: Claude Code:claude-fable-5-1

* ci: derive pyperformance comment target from trusted workflow_run metadata

pr_number.txt came from the artifact a `pull_request` run uploads, which a
fork could tamper with to make this privileged `workflow_run` comment on an
arbitrary PR/issue. Resolve the PR from context.payload.workflow_run instead
(falling back to a commit-associated open PR lookup for workflow_dispatch
runs), and escape any HTML comments already present in diff.md so they can't
be mistaken for the marker.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* ci: grant actions:read to the pyperformance comment workflow

download-artifact needs actions:read to fetch another run's artifact by
run-id. Specifying a permissions block sets every unlisted scope to none, so
without this the cross-run download silently failed for fork PRs -- the
scenario this workflow exists for -- continue-on-error masked it, and the
comment step found no diff.md and returned without posting.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: kill the whole process group on a benchmark timeout

subprocess.run's own timeout only terminates the direct pyperformance
process; pyperf re-execs the target interpreter as a child, which can
survive the timeout and keep burning CPU into the next benchmark's
measurement. Run each benchmark in its own session/process group instead,
and on timeout SIGKILL the whole group via os.killpg.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: compute the head-vs-base cell from head_vs_base directly

The cell was derived from base_vs_cpython and head_vs_cpython, both of which
are None when a benchmark has no CPython time -- so it rendered "-" even
though base and head both had valid times and head_vs_base was already
computed. Use that precomputed ratio instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: invalidate the resumed catalog when the target executable changes

catalog.json records results without any fingerprint of target_python, and
resume skips benchmarks by name alone, so a local rebuild (or swapping the
target) under the same --label could silently reuse stale measurements.
Store a sha256 of the executable's contents alongside the catalog and, when
it no longer matches, ignore the existing catalog and re-run everything.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* ci: fall back to github.sha for the head checkout on workflow_dispatch

github.event.pull_request.head.sha is empty on a workflow_dispatch run (no
pull_request payload), so `git checkout --quiet "" --` failed with "fatal:
invalid reference" on this non-optional step, aborting every manual run
before it could measure or render results.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: resolve --out/--cache-dir to absolute paths

Every benchmark subprocess runs with cwd=work_dir (under --cache-dir), so a
relative --out or --cache-dir passed on the command line resolved against
that directory instead of the one run_all.py was invoked from, breaking
catalog output, the pyperformance binary path, and PIP_FIND_LINKS. Both
default to absolute paths already; resolve them up front so a relative
override behaves the same way.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: persist catalog invalidation before the new fingerprint

The fingerprint file was rewritten before the invalidated catalog was ever
written back to disk. An interruption between the two (e.g. a crash during
the first benchmark of the re-run) left a fingerprint matching the new
executable pointing at a catalog.json still full of results measured
against the old one, so the next run would trust it as fresh. Write the
reset (empty) catalog first, then record the fingerprint.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: show benchmarks that fail on both base and head

Rows were dropped whenever neither side had a mean, which also hid a
benchmark that failed or timed out identically on base and head -- e.g. a
C-extension gap unrelated to the PR under review. Only skip a benchmark
never attempted on either commit; keep rows with a fail/timeout status so
they still show up in the table.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: write catalog.json atomically

write_catalog runs after every single benchmark, and Path.write_text
truncates the file before writing the replacement. An interruption
mid-write left catalog.json both missing every earlier result and invalid
JSON, so the next run's resume logic failed outright at json.loads(). Write
to a temporary sibling file and rename it into place instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: fix passed count and median population in the summary table

"Benchmarks passed" counted len(base_ratios)/len(head_ratios), which require
a *CPython* ratio too -- a CPython-only failure hid an otherwise-passing
benchmark from both sides' counts. Count actual "ok" status per side
instead.

The two medians were also computed over independently-filtered
populations: whichever benchmarks had a valid ratio on that side alone. A
benchmark that regressed to failure on only one side dropped out of only
that side's median, which could shift it well beyond what any surviving
benchmark's timing actually changed by. Restrict both medians to
benchmarks with a valid ratio on both sides, and label the population size.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: include RUSTPYTHONPATH's stdlib in the executable fingerprint

The catalog-invalidation fingerprint hashed only the executable's bytes, but
a RustPython binary copied away from its checkout finds its stdlib through
RUSTPYTHONPATH -- pyperf re-execs the target interpreter into a venv and
forwards that variable so it can still find Lib/. Changing that path, or
editing the files under it, without rebuilding the binary left resume
trusting results measured against a now-different stdlib. Fold its contents
into the fingerprint too.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: require an explicit ok/fail status for pass/fail transitions

only_head/only_base flagged a benchmark as newly passing or no longer
passing based only on whether the other side had a mean, so a benchmark
never attempted on one side (e.g. a partial --benchmarks run) was reported
as a regression or fix it never was. Require the other side's status to be
an actual fail/timeout, not just missing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: don't gate the head/base geometric mean on a CPython ratio

The summary panel -- pass counts and the head/base geometric mean, neither
of which need a CPython comparison -- only rendered when at least one
benchmark also had a valid ratio against CPython on both sides. A build
with a perfectly good head-vs-base comparison but no common CPython result
lost the whole panel, including the one aggregate that didn't depend on
CPython at all.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: normalize RUSTPYTHONPATH and extract main() into named steps

Fix: a relative RUSTPYTHONPATH was fingerprinted relative to this script's
invocation directory but resolved by pyperf's subprocess relative to
work_dir (its cwd), so a relative value could be hashed against the wrong
directory entirely, or fail to resolve at runtime. Resolve it to an
absolute path up front, alongside --out and --cache-dir.

Refactor: main() had accumulated argparse setup, executable resolution, and
the fingerprint/resume block inline, each wrapped in an explanatory comment
-- a sign the function was doing too much rather than that it needed more
narration. Extracted parse_args(), resolve_target_python(), and
load_resumable_catalog() so main() reads as a short sequence of named
steps and each comment sits next to the one function it actually explains.
No behavior change; verified with unit tests against the extracted
functions (fingerprint reacting to RUSTPYTHONPATH, resume picking up a
prior catalog, invalidation on an executable change).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: split pr_diff.py's main() and fix a status-transition gap

Fix: only_head was still gated on have_base, which only asks whether *any*
base benchmark produced a timing -- so a benchmark that flipped from
failing to passing went unreported whenever every other base benchmark
also happened to fail. Status transitions don't need that gate; they
already require an explicit ok/fail/timeout status on both sides.

Refactor: main() had grown into one long function mixing argument parsing,
catalog loading, row computation, and three separate rendering concerns.
Split it into parse_args(), load_base_catalog(), build_rows(),
render_intro(), render_summary_panel(), render_table(), and
find_transitions(), each documenting the one thing it decides. No behavior
change beyond the fix above; re-verified against every scenario exercised
in the last several fixes (dual-fail rows, geo mean without a CPython
ratio, unattempted benchmarks, and the have_base gap) plus the existing
manual smoke tests.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* pyperformance: don't resolve an empty RUSTPYTHONPATH to the cwd

The normalization only checked "RUSTPYTHONPATH" in os.environ, so a set-but-
empty value (RUSTPYTHONPATH="") resolved to the current directory via
Path("").resolve(). executable_fingerprint() would then recursively hash
every file under wherever run_all.py was invoked from -- including its own
results directory while writing to it -- causing spurious catalog
invalidation and a lot of pointless hashing. Check for a nonempty value
instead, matching the truthiness check already used everywhere else this
variable is read.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

* docs(pyperformance): distinguish the host runner from the benchmarked target

A reviewer read "pyperformance cannot be installed as-is on RustPython" and
reasonably asked why RustPython would need to support pyperformance's CLI at
all, since it's normally run as a command under any Python (see
https://github.com/RustPython/RustPython/pull/8691#discussion_r3997957942).

It doesn't: the pyperformance CLI (the host process) always runs under a
real CPython regardless of --python. What actually needs psutil/pyperf
importable is the *benchmark* subprocess -- pyperf re-execs the --python
target and that subprocess itself does `import pyperf`. Spell out that
host/worker split up front instead of leading with "cannot be installed".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wy8J7LpmdYjesTDonNoYkv

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-13 15:30:21 +09:00

267 lines
10 KiB
Python

#!/usr/bin/env python3
"""Render a base/head/CPython pyperformance comparison as a PR comment.
`compare.py` puts one catalog next to one other catalog, which is the right
shape for "how far is RustPython from CPython". A pull request needs a third
column -- the base commit -- and it needs all three measured *in the same CI
job*, back to back on one runner: a ratio between two numbers that were
measured on different machines can move by more than the change under review
did, so a cross-run comparison cannot tell a real regression from a runner
that happened to be slower that day.
Reads `<results-dir>/<label>/catalog.json` for the three labels and writes a
Markdown comment body (and optionally the same data as JSON).
Usage:
python3 scripts/pyperformance/pr_diff.py \\
--cpython cpython --base base --head head \\
--results-dir "$RUNNER_TEMP/pyperf-results" \\
--md diff.md --json diff.json
"""
from __future__ import annotations
import argparse
import json
import statistics
from pathlib import Path
from compare import load_catalog, parse_mean_seconds
MARKER = "<!-- pyperformance-local-diff -->"
# Below this, a head/base difference is indistinguishable from run-to-run
# noise on a shared CI runner, so it is rendered as "~" rather than a number
# that invites over-reading.
NOISE = 0.03
def fmt_ratio(value: float | None) -> str:
return "-" if value is None else f"{value:.2f}x"
def fmt_change(base: float | None, head: float | None) -> str:
"""Head vs. base as a percentage, blanked out inside the noise floor."""
if not base or not head:
return "-"
change = head / base - 1.0
if abs(change) < NOISE:
return "~"
return f"{change * 100:+.1f}%"
def parse_args() -> argparse.Namespace:
parser = argparse.ArgumentParser(
description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter
)
parser.add_argument("--cpython", default="cpython", help="CPython catalog label")
parser.add_argument("--base", default="base", help="base-commit catalog label")
parser.add_argument("--head", default="head", help="head-commit catalog label")
parser.add_argument(
"--results-dir",
type=Path,
required=True,
help="parent directory containing <label>/catalog.json",
)
parser.add_argument("--md", type=Path, required=True, help="Markdown output file")
parser.add_argument("--json", type=Path, help="optional JSON output file")
parser.add_argument(
"--cpython-version",
default="CPython",
help="version string to label the CPython column with",
)
return parser.parse_args()
def load_base_catalog(results_dir: Path, label: str) -> tuple[dict, bool]:
"""Load the base-commit catalog, if any.
The base commit is the column that makes this a review aid rather than a
status report, but it is also the one that can go missing: it may fail to
build, or predate something the benchmarks now need. The caller falls
back to head against CPython alone when nothing here produced a usable
time, rather than failing the whole comparison.
"""
base = {}
if (results_dir / label / "catalog.json").exists():
base = load_catalog(results_dir, label)
have_base = any(parse_mean_seconds(r.get("mean")) for r in base.values())
return base, have_base
def build_rows(cpython: dict, base: dict, head: dict) -> list[dict]:
rows = []
for name in sorted(set(cpython) | set(base) | set(head)):
c = parse_mean_seconds((cpython.get(name) or {}).get("mean"))
b = parse_mean_seconds((base.get(name) or {}).get("mean"))
h = parse_mean_seconds((head.get(name) or {}).get("mean"))
rows.append(
{
"benchmark": name,
"cpython_mean": (cpython.get(name) or {}).get("mean") or "",
"base_mean": (base.get(name) or {}).get("mean") or "",
"head_mean": (head.get(name) or {}).get("mean") or "",
"base_status": (base.get(name) or {}).get("status", "missing"),
"head_status": (head.get(name) or {}).get("status", "missing"),
"base_vs_cpython": (b / c) if (b and c) else None,
"head_vs_cpython": (h / c) if (h and c) else None,
"head_vs_base": (h / b) if (h and b) else None,
}
)
return rows
def render_intro(have_base: bool, cpython_version: str) -> list[str]:
if have_base:
return [
"All three interpreters were measured back to back in this one job, "
"so they share the exact same CPU and kernel. Ratios are "
f"`time / {cpython_version} time` -- lower is better. A "
f"head/base difference smaller than {NOISE:.0%} is shown as `~`; CI "
"runners are not quiet enough to read more into it than that."
]
return [
"No usable result for the base commit -- it did not build, or none "
"of its benchmarks produced a time -- so this is head against "
f"{cpython_version} alone, both measured back to back in this "
"one job. Ratios are `time / {} time`; lower is better.".format(cpython_version)
]
def render_summary_panel(
rows: list[dict], have_base: bool, cpython_version: str
) -> list[str]:
"""The "| | base | head |" mini-table: pass counts, the median slowdown
vs. CPython, and the head/base geometric mean.
Each row is independently gated on having the data it needs: the two
medians are restricted to benchmarks with a valid ratio on *both* sides,
so a benchmark that regressed to failure on only one side can't drop out
of only that side's population and skew the comparison; "Benchmarks
passed" and the geometric mean don't depend on CPython at all, so they
must not disappear just because no benchmark had a usable CPython
comparison.
"""
if not have_base:
return []
common_vs_cpython = [
r for r in rows if r["base_vs_cpython"] and r["head_vs_cpython"]
]
base_ratios = [r["base_vs_cpython"] for r in common_vs_cpython]
head_ratios = [r["head_vs_cpython"] for r in common_vs_cpython]
base_passed = sum(1 for r in rows if r["base_status"] == "ok")
head_passed = sum(1 for r in rows if r["head_status"] == "ok")
both = [r for r in rows if r["head_vs_base"]]
out = ["| | base | head |", "| --- | ---: | ---: |"]
if base_ratios and head_ratios:
out.append(
f"| Median slowdown vs. {cpython_version} "
f"({len(common_vs_cpython)} common) "
f"| {statistics.median(base_ratios):.2f}x "
f"| {statistics.median(head_ratios):.2f}x |"
)
out.append(f"| Benchmarks passed | {base_passed} | {head_passed} |")
if both:
geo = statistics.geometric_mean([r["head_vs_base"] for r in both])
out.append(f"| Geometric mean, head/base ({len(both)} common) | | {geo:.3f} |")
out.append("")
return out
def render_table(rows: list[dict], have_base: bool, cpython_version: str) -> list[str]:
if have_base:
out = [
f"| Benchmark | {cpython_version} | base | head "
f"| base/{cpython_version} | head/{cpython_version} "
"| head vs. base |",
"| --- | ---: | ---: | ---: | ---: | ---: | ---: |",
]
else:
out = [
f"| Benchmark | {cpython_version} | head | head/{cpython_version} |",
"| --- | ---: | ---: | ---: |",
]
for r in sorted(rows, key=lambda r: r["head_vs_base"] or r["head_vs_cpython"] or 0):
# A row with no mean on either side but a fail/timeout status is still
# worth showing -- e.g. a C-extension gap that fails identically on
# base and head. Only a benchmark never attempted on either commit
# (no entry in that catalog at all) has nothing to report.
if r["base_status"] == "missing" and r["head_status"] == "missing":
continue
head_cell = r["head_mean"] or "({})".format(r["head_status"])
if not have_base:
out.append(
f"| {r['benchmark']} | {r['cpython_mean'] or '-'} | {head_cell} "
f"| {fmt_ratio(r['head_vs_cpython'])} |"
)
continue
base_cell = r["base_mean"] or "({})".format(r["base_status"])
out.append(
f"| {r['benchmark']} | {r['cpython_mean'] or '-'} "
f"| {base_cell} | {head_cell} "
f"| {fmt_ratio(r['base_vs_cpython'])} | {fmt_ratio(r['head_vs_cpython'])} "
f"| {fmt_change(1.0, r['head_vs_base'])} |"
)
return out
def find_transitions(rows: list[dict]) -> tuple[list[str], list[str]]:
"""Benchmarks whose pass/fail status flipped between base and head.
A transition claim needs an actual *fail/timeout* status on the other
side, not just a missing entry: a benchmark never attempted there (e.g.
a partial --benchmarks run) isn't a regression or a fix, just no data
point. This intentionally doesn't gate on `have_base` (whether *any*
base benchmark produced a timing) -- a benchmark can still validly flip
from failing to passing even when every other base benchmark failed too.
"""
only_head = [
r["benchmark"]
for r in rows
if r["head_status"] == "ok" and r["base_status"] in ("fail", "timeout")
]
only_base = [
r["benchmark"]
for r in rows
if r["base_status"] == "ok" and r["head_status"] in ("fail", "timeout")
]
return only_head, only_base
def main() -> None:
args = parse_args()
cpython = load_catalog(args.results_dir, args.cpython)
head = load_catalog(args.results_dir, args.head)
base, have_base = load_base_catalog(args.results_dir, args.base)
rows = build_rows(cpython, base, head)
title = (
"base vs. head vs. CPython (same runner)"
if have_base
else "head vs. CPython (same runner)"
)
out = [MARKER, f"### pyperformance: {title}", ""]
out += render_intro(have_base, args.cpython_version)
out.append("")
out += render_summary_panel(rows, have_base, args.cpython_version)
out += render_table(rows, have_base, args.cpython_version)
only_head, only_base = find_transitions(rows)
if only_head:
out += ["", f"Newly passing on head: {', '.join(only_head)}."]
if only_base:
out += ["", f"No longer passing on head: {', '.join(only_base)}."]
args.md.write_text("\n".join(out) + "\n")
if args.json:
args.json.write_text(json.dumps(rows, indent=2) + "\n")
if __name__ == "__main__":
main()