bpo-41247: asyncio.set_running_loop() cache running loop holder by tontinton · Pull Request #21401 · python/cpython
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
approved these changes
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request
…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 <tony.solomonik@gmail.com>
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request
…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 <tony.solomonik@gmail.com>
miss-islington added a commit that referenced this pull request
…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 <tony.solomonik@gmail.com>
shihai1991 pushed a commit to shihai1991/cpython that referenced this pull request
…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