iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 101: Rename to `add_to_pydotorg.py` (#3889)

This commit is contained in:
Hugo van Kemenade 2024-08-04 17:50:07 +03:00 committed by GitHub
parent 219ea7d3e5
commit 81c5900f25
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
peps/pep-0101.rst
View File

@ -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=<username>:<python.org-api-key> python add-to-pydotorg.py <version>
AUTH_INFO=<username>:<python.org-api-key> python add_to_pydotorg.py <version>
This walks the correct download directory for ``<version>``,
looks for files marked with ``<version>``, 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