Skip to content

stubgen: never generate variable initializer #10623

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 3 commits into from
Jun 10, 2021

Conversation

srittau
Copy link
Contributor

@srittau srittau commented Jun 10, 2021

Description

Previously, the generation of a variable initialized (= ...) was
inconsistent between top-level and class-level variables. Since the
initializer has no function in stubs, stubgen will now never generate
it.

Test Plan

Existing unit tests were updated.

Previously, the generation of a variable initialized (= ...) was
inconsistent between top-level and class-level variables. Since the
initializer has no function in stubs, stubgen will now never generate
it.
@srittau
Copy link
Contributor Author

srittau commented Jun 10, 2021

Gentle ping. If this is merged, I can merge it into #10626.

@JelleZijlstra JelleZijlstra merged commit 8664ada into python:master Jun 10, 2021
@JelleZijlstra
Copy link
Member

Pong!

@srittau srittau deleted the stubgen-no-initializer branch June 10, 2021 23:25
@srittau srittau mentioned this pull request Jun 11, 2021
JukkaL pushed a commit that referenced this pull request Jun 21, 2021
Previously, the generation of a variable initialized (= ...) was
inconsistent between top-level and class-level variables. Since the
initializer has no function in stubs, stubgen will now never generate
it.
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.

3 participants