Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 25, 2022
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
360a202
PEP 13: Fix broken link.
oraluben Jan 25, 2022
ef49d92
PEP 245: Fix broken link.
oraluben Jan 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pep-0013.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion pep-0245.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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::

Expand Down