Python documentation is now available in German

The official Python documentation now has a German edition. The Python project announced it on September 26, 2026, and the pages live at docs.python.org/de/3/. It matters because German speakers can now learn the language from its own reference, not from third-party books or blog posts.

The announcement came from Stan Ulbrych on the Python Insider blog. "We're excited to announce that the Python documentation is now available in German (Deutsch)!" he wrote. He credited the community volunteers who did the translation work.

What is translated so far

The German edition is complete where it counts first, and thin everywhere else. The project's translation dashboard at translations.python.org tracks two numbers for each language.

Measure	German progress
Core documentation	100%
Core progress in the last 30 days	23.79%
Full documentation	9.17%
Full progress in the last 30 days	5.87%

So roughly a quarter of the core set was finished in the final month before launch. The full documentation is a far bigger body of text. It includes the standard library reference, which describes every built-in module in detail.

The German site offers several Python versions. Its version menu lists Python 3.14.7 as the current stable release. It also offers 3.15, which is in pre-release, and 3.16, which is still in development.

Why a language appears only when its core is done

Python's rules for translations come from PEP 545, a Python Enhancement Proposal. A PEP is the formal design document the project uses to decide how things work.

PEP 545 sets a bar before a language appears in the documentation's language menu. Three parts must be 100% translated: the page on reporting bugs, the tutorial, and the reference for built-in functions. That is why a new language can go live while most of its pages are still in English. The pieces a beginner reads first are finished; the long tail comes later.

The same PEP fixes the web address pattern, docs.python.org/LANGUAGE/VERSION/. It also requires one named coordinator per language. For German, the Python Developer's Guide names Swen Bachmann as that coordinator. The translation files live in his GitHub repository, python-docs-de, which shows 361 commits.

How the translation pipeline works

Translators never edit the documentation pages directly. According to the Developer's Guide, they work in gettext PO files. Gettext is a common toolkit for translating software. A PO file lists each English sentence next to a slot for its translation.

Sphinx, the tool that builds Python's documentation, generates those files from the English source. When translators finish, build scripts pull the files in and publish them to docs.python.org automatically. The German team manages its work through Transifex, a web platform for translation projects.

Contributors must first accept a documentation contribution agreement. Under PEP 545, that offers their work under the CC0 license, a public-domain dedication. German joins 27 active translation projects, which include French, Spanish, Japanese, Russian, Hungarian and both forms of Chinese.

What this means for developers

If you teach Python to German speakers, point them at docs.python.org/de/3/ for the tutorial and the built-in functions reference now. Those parts are fully translated. For the standard library reference, expect most pages to still read in English, since the full set is at 9.17%.

Check the version in any link you share. The German site offers several versions, from 2.6 up to the 3.16 development docs. A link to /de/3/ follows the current stable release, while a link with a version number stays fixed. Use the fixed form in course material you do not plan to update.

If you write German and know Python, this is one of the easier ways to contribute to the project. You translate PO entries through Transifex, and the Developer's Guide explains the setup. The 9.17% figure shows how much of the library reference still needs hands.

Keep your terms consistent. The Developer's Guide asks translators to respect technical naming, so names like dict or asyncio stay as they are. Only the prose around them changes.

Last, watch the dashboard if your team works in another language. The same 100% core rule decides when that edition appears in the language menu.