Skip to content

Treat varargs as legal context in default lambda argument (Take 2) #2796

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 4 commits into from
Feb 6, 2017

Conversation

elazarg
Copy link
Contributor

@elazarg elazarg commented Feb 2, 2017

Fix #2764.

Reopen #2770, fixing the issue in #2790 triggered by a context with more parameters than a varargs lambda.

@JukkaL
Copy link
Collaborator

JukkaL commented Feb 6, 2017

Thanks for the fix! This now seems to work with our internal repos.

@JukkaL JukkaL merged commit 31333d8 into python:master Feb 6, 2017
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.

Incompatible types in assignment with --strict-optional for a: Callable[..., None] = lambda *a, **k: None
2 participants