Thanks to visit codestin.com
Credit goes to github.com

Skip to content

gh-85747: Active voice & suggested edits, 'running/stopping loop' & 'callbacks' subsections of asyncio-eventloop.rst #100270

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

Merged
merged 10 commits into from
Feb 7, 2023

Conversation

bskinn
Copy link
Contributor

@bskinn bskinn commented Dec 15, 2022

Another docs revision PR of asyncio-eventloop.rst per #85747.

There are a couple of spots here where I think more explanation than was already present will be useful. I've attempted explanations of my own, but they may be incorrect. I'll mark these with review comments shortly.

I didn't change much of the passive voice related to callback interactions, within the description text of methods that work with callbacks. All the attempts I made to cast those descriptions in active voice seemed to degrade readability.

Loop run/stop section, and callbacks section.
@netlify
Copy link

netlify bot commented Dec 15, 2022

Deploy Preview for python-cpython-preview ready!

Name Link
🔨 Latest commit 7c3fb58
🔍 Latest deploy log https://app.netlify.com/sites/python-cpython-preview/deploys/639b3f604a5a2b000a14de44
😎 Deploy Preview https://deploy-preview-100270--python-cpython-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@bedevere-bot bedevere-bot added docs Documentation in the Doc dir skip news labels Dec 15, 2022
Copy link
Member

@CAM-Gerlach CAM-Gerlach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added some clarifications on some further points of confusion (that I had to look up in the code, or guess on), as well as refined the phrasing and fixed a few other issues. Thanks!

@gvanrossum
Copy link
Member

I'm unsubscribing for now, but do ping me if you need me to arbitrate some choice!

bskinn and others added 4 commits January 31, 2023 20:52
I also prefer the more verbose phrasing
that doesn't start the sentence with a 
lowercase letter.

Remove the spurious whitespace.

Co-authored-by: Guido van Rossum <[email protected]>
Co-authored-by: C.A.M. Gerlach <[email protected]>
@bskinn
Copy link
Contributor Author

bskinn commented Feb 2, 2023

@gvanrossum -- I believe this PR is ready for consideration for merge. Thank you for the input & guidance!

Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sorry, but there are still too many grammatical oddities to approve the PR. Please ask one of the docs folks (e.g. @CAM-Gerlach) to go over the grammar carefully.

@bedevere-bot
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@arhadthedev
Copy link
Member

Please ask one of the docs folks [...] to go over the grammar carefully.

@python/proofreaders

@CAM-Gerlach CAM-Gerlach self-requested a review February 4, 2023 23:37
@CAM-Gerlach CAM-Gerlach added needs backport to 3.10 only security fixes needs backport to 3.11 only security fixes labels Feb 4, 2023
Copy link
Member

@CAM-Gerlach CAM-Gerlach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After some more consideration and thought, various suggestions to improve the readability and clarity of the grammar and phrasing and avoid regressions on that front.

@terryjreedy
Copy link
Member

I am taking a look,

@bskinn
Copy link
Contributor Author

bskinn commented Feb 6, 2023

@CAM-Gerlach, it seems like you and @terryjreedy are in a good flow for further polishing here.

Do you have write access on my fork? If not, do you want it? I don't want my pace of review to hold up applying changes to the PR branch.

@CAM-Gerlach
Copy link
Member

Thanks @bskinn . I've applied the review comments and also moved the return line up to right after the call_soon summary line, as mentioned above.

Just FYI, you can just batch-apply all desired review comments in one go by clicking on the Files changed, clicking Add to batch on each suggestion, and finally pressing Commit.

@bskinn
Copy link
Contributor Author

bskinn commented Feb 6, 2023

Just FYI, you can just batch-apply all desired review comments in one go by clicking on the Files changed, clicking Add to batch on each suggestion, and finally pressing Commit.

Yup, I know -- super handy feature! I wasn't sure which suggestions were 'final', or if there was more discussion coming...so, I didn't feel comfortable committing anything without a thorough review that I couldn't be sure when I could carry out.

Copy link
Member

@CAM-Gerlach CAM-Gerlach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from my end, now

@gvanrossum gvanrossum merged commit c4de6b1 into python:main Feb 7, 2023
@miss-islington
Copy link
Contributor

Thanks @bskinn for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11.
🐍🍒⛏🤖

@miss-islington
Copy link
Contributor

Sorry, @bskinn and @gvanrossum, I could not cleanly backport this to 3.11 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker c4de6b1d52304a0a9cdfafc1dad5098993710404 3.11

@miss-islington
Copy link
Contributor

Sorry @bskinn and @gvanrossum, I had trouble checking out the 3.10 backport branch.
Please retry by removing and re-adding the "needs backport to 3.10" label.
Alternatively, you can backport using cherry_picker on the command line.
cherry_picker c4de6b1d52304a0a9cdfafc1dad5098993710404 3.10

@bedevere-bot
Copy link

GH-102005 is a backport of this pull request to the 3.10 branch.

@bedevere-bot
Copy link

GH-102006 is a backport of this pull request to the 3.11 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.11 only security fixes label Feb 17, 2023
bskinn added a commit to bskinn/cpython that referenced this pull request Feb 17, 2023
…ing loop' & 'callbacks' subsections of asyncio-eventloop.rst (pythonGH-100270)

Co-authored-by: C.A.M. Gerlach <[email protected]>
Co-authored-by: Terry Jan Reedy <[email protected]>.
(cherry picked from commit c4de6b1)

Co-authored-by: Brian Skinn <[email protected]>
gvanrossum pushed a commit that referenced this pull request Feb 18, 2023
…op' & 'callbacks' subsections of asyncio-eventloop.rst (GH-100270) (#102006)

Note: the `timeout` parameter was not added until 3.12.

(cherry picked from commit c4de6b1)

Co-authored-by: C.A.M. Gerlach <[email protected]>
Co-authored-by: Terry Jan Reedy <[email protected]>.
Co-authored-by: Brian Skinn <[email protected]>
gvanrossum pushed a commit that referenced this pull request Feb 18, 2023
…op' & 'callbacks' subsections of asyncio-eventloop.rst (gh-100270) (#102005)

Note: The `timeout` parameter was not added until Python 3.12.

(cherry picked from commit c4de6b1)

Co-authored-by: C.A.M. Gerlach <[email protected]>
Co-authored-by: Terry Jan Reedy <[email protected]>
@bskinn bskinn deleted the active-voice-asyncio-2 branch February 18, 2023 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip news
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants