Executive Summary
I read the PSF announcement about the PSF, Python, and Jython wikis finally coming back to life after being locked read-only since February 2026. What's interesting is that this time they moved entirely to GitHub Pages with a pull-request-based contribution workflow, rather than just turning the old wiki engine back on.
The Problem Being Solved
From what I gathered, the main problem wasn't the wiki content itself, but the infrastructure. The old wiki was flooded with automated traffic — mostly AI bots trying to scrape the entire internet — to the point that the server frequently went down, and the alerts often woke up PSF's single on-call staff member in the middle of the night (they said the number of staff for this would be increased). On top of that, some wiki pages were still built on Python 2, which has been EOL since 1 Januari 2020 and no longer receives security patches. The combination of these two things is what ultimately led PSF to lock the wiki as read-only without notifying the community first — a decision they themselves admit was quite painful for longtime contributors who had maintained the wiki for years.
Key Features and Code Example
The solution: generate the wiki as a static site via GitHub Pages. This automatically eliminates the server-side bot scraping problem since there's no longer a dynamic backend that can be overloaded, while also cutting security risk since there's no more Python 2 code running on the server. PSF also chose GitHub because it's already home to CPython and python.org, making overall hosting stewardship easier for them. The most significant change, in my view, is in the contribution model. Previously, the Python and Jython wikis could be edited directly through an invitation system from existing editors, while the PSF wiki was already permission-based. Now all three have been unified into a permission-based model via a GitHub repository, and anyone in the community can propose changes through a pull request — they even said it can be done directly from a code editor if you want. Here's an illustration of the contribution workflow, similar to a typical GitHub pull request workflow (the repo name below is just an example, not the official name):
# Ilustrasi alur kontribusi ke salah satu wiki baru
git clone https://github.com/<org>/<nama-wiki>.git
cd <nama-wiki>
git checkout -b perbaiki-halaman-faq
# edit file markdown halaman wiki
git add .
git commit -m "Perbarui halaman FAQ"
git push origin perbaiki-halaman-faq
gh pr create --title "Perbarui halaman FAQ" --body "Update info FAQ yang sudah usang"PSF also said that longtime contributors previously known as wiki stewards will be directly given write access to the new Python wiki.
Impact and Upgrade Notes
For anyone who used to edit the Python/Jython wiki the old way, this is a fairly big change: no more instant edits without review — every change now goes through pull request review on GitHub. PSF describes this as a trade-off they consciously chose — with granular control and per-PR review, they can maintain uptime without worrying about being overwhelmed by AI bot traffic again. If you want to contribute to the new PSF Wiki, Python Wiki, or Jython Wiki, PSF asks that you first read the README file in each repository to learn the details of the process.
---
First announced on Python Software Foundation. Read the original source for full details.