Skip to content
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

[backport] [used before def] correctly handle walrus operator (#14646) #14654

Merged
merged 1 commit into from
Feb 9, 2023

Conversation

ilinum
Copy link
Collaborator

@ilinum ilinum commented Feb 8, 2023

Fixes #14626.

I believe changing the way that we analyze call expression makes sense (first, we analyze the callee, then we analyze the arguments).

Fixes python#14626.

I believe changing the way that we analyze call expression makes sense
(first, we analyze the callee, then we analyze the arguments).
@hauntsaninja
Copy link
Collaborator

I think you might need a commit like 1368338 to avoid confusing https://github.com/mypyc/mypy_mypyc-wheels when this is merged

@github-actions

This comment was marked as outdated.

@ilinum
Copy link
Collaborator Author

ilinum commented Feb 9, 2023

I think you might need a commit like 1368338 to avoid confusing https://github.com/mypyc/mypy_mypyc-wheels when this is merged

Thanks for pointing this out! Do you know what would happen if I did that?

@ilinum ilinum merged commit c090ca2 into python:release-1.0 Feb 9, 2023
@ilinum ilinum deleted the 1.0/walrus branch February 9, 2023 17:16
@hauntsaninja
Copy link
Collaborator

I think it's not the worst, but causes some confusion and some failures. I think the trigger wheel build tries to push a duplicate tag to the wheels repo and it fails (or maybe it overwrites the previous tag). I also seem to remember some issue when the wheels repo makes a release (to share the artifacts) if the release already exists

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.

2 participants