From 81c5900f2510c6f756d5f57602b0869ff320799f Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Sun, 4 Aug 2024 17:50:07 +0300 Subject: [PATCH] PEP 101: Rename to `add_to_pydotorg.py` (#3889) --- peps/pep-0101.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/peps/pep-0101.rst b/peps/pep-0101.rst index d36ec2e2b..c21e18145 100644 --- a/peps/pep-0101.rst +++ b/peps/pep-0101.rst @@ -647,11 +647,11 @@ permissions. - Populate the release with the downloadable files. Your friend and mine, Georg Brandl, made a lovely tool - called ``add-to-pydotorg.py``. You can find it in the + called ``add_to_pydotorg.py``. You can find it in the `python/release-tools`_ repo (next to ``release.py``). You run the tool on ``downloads.nyc1.psf.io``, like this:: - AUTH_INFO=: python add-to-pydotorg.py + AUTH_INFO=: python add_to_pydotorg.py This walks the correct download directory for ````, looks for files marked with ````, and populates @@ -664,8 +664,8 @@ permissions. keep it fresh. If new types of files are added to the release, someone will need to - update ``add-to-pydotorg.py`` so it recognizes these new files. - (It's best to update ``add-to-pydotorg.py`` when file types + update ``add_to_pydotorg.py`` so it recognizes these new files. + (It's best to update ``add_to_pydotorg.py`` when file types are removed, too.) The script will also sign any remaining files that were not