This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Typo in pep-0636 page
Type: enhancement Stage: resolved
Components: Documentation Versions: Python 3.10
process
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: docs@python Nosy List: adrigs, docs@python, raulcd, xtreak
Priority: normal Keywords:

Created on 2021-10-05 08:10 by adrigs, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (4)
msg403201 - (view) Author: AdrienGoncalves (adrigs) Date: 2021-10-05 08:10
There is a typo in https://www.python.org/dev/peps/pep-0636/#composing-patterns

The second sentence in the first paragraph : "[...] we have being doing that implicitly in the examples above."

When it should be "[...] we have been doing that implicitly in the examples above."
msg403222 - (view) Author: Raúl Cumplido (raulcd) * Date: 2021-10-05 10:46
Thanks! I have created a PR for it on the peps repo.
https://github.com/python/peps/pull/2101
I can't seem to be able to link the Github PR correctly. Probably because it's not on the cpython repo.
msg403224 - (view) Author: Raúl Cumplido (raulcd) * Date: 2021-10-05 10:53
This has been merged on the peps repo and can be closed.
msg403228 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2021-10-05 11:01
Thanks for the report and fix. Closing it as third party since PEPs are maintained in different repo using GitHub issues.
History
Date User Action Args
2022-04-11 14:59:50adminsetgithub: 89533
2021-10-05 11:01:23xtreaksetstatus: open -> closed

nosy: + xtreak
messages: + msg403228

resolution: third party
stage: resolved
2021-10-05 10:53:34raulcdsetmessages: + msg403224
2021-10-05 10:46:21raulcdsetnosy: + raulcd
messages: + msg403222
2021-10-05 08:10:47adrigscreate