Skip to content

bpo-41247: asyncio.set_running_loop() cache running loop holder #21401

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 1 commit into from
Jul 8, 2020

Conversation

tontinton
Copy link
Contributor

@tontinton tontinton commented Jul 8, 2020

The running loop holder cache variable was always set to NULL when
calling set_running_loop.

Now set_running_loop saves the newly created running loop holder in the
cache variable for faster access in get_running_loop.

https://bugs.python.org/issue41247

Automerge-Triggered-By: @1st1

The running loop holder cache variable was always set to NULL when
calling set_running_loop.

Now set_running_loop saves the newly created running loop holder in the
cache variable for faster access in get_running_loop.
@1st1
Copy link
Member

1st1 commented Jul 8, 2020

Wow, what a good catch. Thank you.

@miss-islington
Copy link
Contributor

@tontinton: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit 529f426 into python:master Jul 8, 2020
@miss-islington
Copy link
Contributor

Thanks @tontinton for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 8, 2020
…onGH-21401)

The running loop holder cache variable was always set to NULL when
calling set_running_loop.

Now set_running_loop saves the newly created running loop holder in the
cache variable for faster access in get_running_loop.

Automerge-Triggered-By: @1st1
(cherry picked from commit 529f426)

Co-authored-by: Tony Solomonik <[email protected]>
@bedevere-bot bedevere-bot removed the needs backport to 3.9 only security fixes label Jul 8, 2020
@bedevere-bot
Copy link

GH-21402 is a backport of this pull request to the 3.9 branch.

@bedevere-bot
Copy link

GH-21403 is a backport of this pull request to the 3.8 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 8, 2020
…onGH-21401)

The running loop holder cache variable was always set to NULL when
calling set_running_loop.

Now set_running_loop saves the newly created running loop holder in the
cache variable for faster access in get_running_loop.

Automerge-Triggered-By: @1st1
(cherry picked from commit 529f426)

Co-authored-by: Tony Solomonik <[email protected]>
miss-islington added a commit that referenced this pull request Jul 8, 2020
…1401)

The running loop holder cache variable was always set to NULL when
calling set_running_loop.

Now set_running_loop saves the newly created running loop holder in the
cache variable for faster access in get_running_loop.

Automerge-Triggered-By: @1st1
(cherry picked from commit 529f426)

Co-authored-by: Tony Solomonik <[email protected]>
arun-mani-j pushed a commit to arun-mani-j/cpython that referenced this pull request Jul 21, 2020
…onGH-21401)

The running loop holder cache variable was always set to NULL when
calling set_running_loop.

Now set_running_loop saves the newly created running loop holder in the
cache variable for faster access in get_running_loop.

Automerge-Triggered-By: @1st1
shihai1991 pushed a commit to shihai1991/cpython that referenced this pull request Aug 20, 2020
…onGH-21401)

The running loop holder cache variable was always set to NULL when
calling set_running_loop.

Now set_running_loop saves the newly created running loop holder in the
cache variable for faster access in get_running_loop.

Automerge-Triggered-By: @1st1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants