polytypo
Locale-correct quotes, dashes, ellipses, apostrophes, symbols and no-break spaces —
one portable spec, designed for byte-identical output across runtimes.
Try it live, no install: polytypo.dev
This is the Python implementation. The full spec — all locales, all rules, worked examples in
each — lives in polytypo/polytypo. This runtime supports
the text and html modes fully, and markdown for the commonmark dialect only — mdx
raises POLYTYPO_INVALID_DIALECT (no MDX/JSX parser is available for Python; see
Supported dialects).
Install
pip install polytypo
Usage
from polytypo import transform
transform("She said, \"it's fine\" -- but I wasn't sure...", locale="en-US")
# She said, “it’s fine”—but I wasn’t sure…
Same input, one locale changed — quotes, dash spacing and all follow the target locale, not a single hardcoded style:
transform('Sie sagte: "Alles gut" -- aber ich war mir nicht sicher...', locale="de-DE")
# Sie sagte: „Alles gut“ – aber ich war mir nicht sicher…
HTML and Markdown are first-class modes, not an afterthought — tags, attributes and fenced code are left alone; only text content is touched:
from polytypo.html import transform
transform('<a title="test... wait">Wait... she said "go on."</a>', locale="en-US")
# <a title="test... wait">Wait… she said “go on.”</a>
polytypo.text, polytypo.html and polytypo.markdown each exclude the parser dependency the
other modes don't need (importing polytypo.text never imports html.parser-based span
extraction or tree-sitter). The aggregate polytypo module supports every mode via a mode
keyword, defaulting to "text". locale has no default anywhere and must always be passed
explicitly — there is no silent fallback to English.
import polytypo
polytypo.transform("...", locale="fr", mode="markdown", dialect="commonmark")
Supported dialects
markdown mode requires a dialect keyword, exactly as the spec requires (no default,
detection is forbidden). This runtime supports dialect="commonmark" (CommonMark plus GFM —
tables, strikethrough, task lists, autolink literals). dialect="mdx" is a real dialect the spec
names, but this runtime has no MDX/JSX parser for it and raises POLYTYPO_INVALID_DIALECT
immediately rather than silently mishandling it — a narrower, honest conformance claim, not a
port defect.
Licence
MIT. See LICENSE.
Release files for polytypo 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| polytypo-1.1.0.tar.gz | 248.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| polytypo-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 338.8 kB
Release files / polytypo-1.1.0.tar.gz
| Download URL | polytypo-1.1.0.tar.gz |
|---|---|
| Size | 248.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d6ae72ba661aa7f22d00879bf9204aed89faa39e142ec3f03ba31461cd5c7e0
|
|
BLAKE2b-256 checksum How to use checksums |
1d6bd8c0f981b6163c2b7748c7b256ed7903c20aac25b5c100f1fc0355215f42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / polytypo-1.1.0-py3-none-any.whl
| Download URL | polytypo-1.1.0-py3-none-any.whl |
|---|---|
| Size | 90.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3df44fe402d835daa8e421010255d25fc6a938880dbccfe05c974b6e546f9d4
|
|
BLAKE2b-256 checksum How to use checksums |
b044fdba2dd24fadfe96f138f9d6002acacd29b590ce0cdae7bf852c1e4d5d5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency log