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

Skip to content

gh-118527: Use _Py_ID(__main__) for main module name #118528

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
May 3, 2024

Conversation

colesbury
Copy link
Contributor

@colesbury colesbury commented May 3, 2024

Most module names are interned and immortalized, but the main module's name was not. This partially addresses a scaling bottleneck in the free-threaded when creating closure concurrently in the main module.

Most module names are interned and immortalized, but the `__main__`
module was not. This partially addresses a scaling bottleneck in the
free-threaded when creating closure concurrently in the main module.
Copy link
Member

@corona10 corona10 left a comment

Choose a reason for hiding this comment

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

LGTM

@colesbury colesbury merged commit 24e643d into python:main May 3, 2024
39 checks passed
@colesbury colesbury deleted the gh-118527-__main__ branch May 3, 2024 15:05
SonicField pushed a commit to SonicField/cpython that referenced this pull request May 8, 2024
…118528)

Most module names are interned and immortalized, but the main
module was not. This partially addresses a scaling bottleneck in the
free-threaded when creating closure concurrently in the main module.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants