-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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.
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
Fix typo in re docs #1113
Fix typo in re docs #1113
Conversation
@berkerpeksag, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ezio-melotti, @birkenfeld and @tiran to be potential reviewers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even if the change is correct, I would prefer a link to the book rather than having to scroll 3 pages. I had to search manually in the doc to find it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a reference to the below seealso block
Doc/library/re.rst
Outdated
@@ -67,7 +67,7 @@ operations; boundary conditions between *A* and *B*; or have numbered group | |||
references. Thus, complex expressions can easily be constructed from simpler | |||
primitive expressions like the ones described here. For details of the theory | |||
and implementation of regular expressions, consult the Friedl book referenced | |||
above, or almost any textbook about compiler construction. | |||
below, or almost any textbook about compiler construction. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a reference to the seealso
block
consult the Friedl book `mastering regular expressions`_ referenced below
.. _mastering regular expressions:
.. seealso::
To try and help move older pull requests forward, we are going through and backfilling 'awaiting' labels on pull requests that are lacking the label. Based on the current reviews, the best we can tell in an automated fashion is that a core developer requested changes to be made to this pull request. If/when the requested changes have been made, please leave a comment that says, |
Reported by Maksym Nikulyak on docs.p.o.
54079e3
to
b0cc540
Compare
Used citation instead of just typo fix.
Thanks @berkerpeksag for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7. |
GH-6200 is a backport of this pull request to the 3.7 branch. |
Reported by Maksym Nikulyak on docs.p.o. (cherry picked from commit a0a42d2) Co-authored-by: Berker Peksag <berker.peksag@gmail.com>
Reported by Maksym Nikulyak on docs.p.o. (cherry picked from commit a0a42d2) Co-authored-by: Berker Peksag <berker.peksag@gmail.com>
GH-6201 is a backport of this pull request to the 3.6 branch. |
Reported by Maksym Nikulyak on docs.p.o. (cherry picked from commit a0a42d2) Co-authored-by: Berker Peksag <berker.peksag@gmail.com>
Reported by Maksym Nikulyak on docs.p.o. (cherry picked from commit a0a42d2) Co-authored-by: Berker Peksag <berker.peksag@gmail.com>
Reported by Maksym Nikulyak on docs.p.o.