PEP 13 and PEP 245: Fix incorrect PEP references (#2267)

* PEP 13: Fix invalid PEP reference
* PEP 245: Fix reference to wrong (duplicate) PEP
This commit is contained in:
Yichen 2022-01-25 15:58:30 +08:00 committed by GitHub
parent 43b77a681a
commit 5e5616dce3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -333,7 +333,7 @@ History of council elections
* January 2019: :pep:`8100`
* December 2019: :pep:`8101`
* December 2020: :pep:`8102`
* December 2021: :pep:`8104`
* December 2021: :pep:`8103`
History of amendments

View File

@ -438,7 +438,7 @@ extension to Python's syntax does not change any existing syntax
in any backward incompatible way.
The new ``from __future__`` Python syntax (:pep:`236`), and the new warning
framework (:pep:`236`) is ideal for resolving this backward
framework (:pep:`230`) is ideal for resolving this backward
incompatibility. To use interface syntax now, a developer could
use the statement::