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

PEP 2026: Fix repeated word typos (#3957) 

Fix duplicated words in PEP 2026
This commit is contained in:
Brian Schubert 2024-09-12 13:30:18 -04:00 committed by GitHub
parent 430987f98a
commit 507d0e53a3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
peps/pep-2026.rst
View File

@ -220,7 +220,7 @@ For example:
removal in Python 3.15 removal in Python 3.15
However, once aware of CalVer, it is immediately obvious from the warning how However, once aware of CalVer, it is immediately obvious from the warning how
long you have to to take action: long you have to take action:
DeprecationWarning: 'ctypes.SetPointerType' is deprecated and slated for DeprecationWarning: 'ctypes.SetPointerType' is deprecated and slated for
removal in Python 3.26 removal in Python 3.26
@ -494,7 +494,7 @@ commands. ``python`` can map to either ``python2`` or ``python3``.
These would need revisiting if the major version changed, and started changing annually. These would need revisiting if the major version changed, and started changing annually.
Four years after Python 2.7's end-of-life, we could recommend ``python`` only Four years after Python 2.7's end-of-life, we could recommend ``python`` only
maps to the the latest Python 3+ version. maps to the latest Python 3+ version.
But what would ``python3`` map to when Python 26.0 is out? But what would ``python3`` map to when Python 26.0 is out?
This would introduce additional complexity and cost. This would introduce additional complexity and cost.