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.

Sign up for GitHub

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

Jump to bottom

(*args: Any, **kwargs: Any) should be treated as ... in function definition #7848

Closed
erictraut opened this issue May 6, 2024 · 1 comment
Closed

(*args: Any, **kwargs: Any) should be treated as ... in function definition #7848

erictraut opened this issue May 6, 2024 · 1 comment
Labels
addressed in next version Issue is fixed and will appear in next published version bug Something isn't working spec compliance

Comments

@erictraut
Copy link
Collaborator

The typing spec was just updated to clarify that any function definition ("def" statement) that includes an explicit or implicit *args: Any, **kwargs: Any should be treated as the equivalent of ..., a gradual type form. Pyright is not currently compliant with this new rule.
@erictraut erictraut added bug Something isn't working spec compliance labels May 6, 2024
erictraut added a commit that referenced this issue May 7, 2024
@erictraut
Changed interpretation of function definitions with (*args: Any, **kw…
dd10c53 
…args: Any) to be `...` in compliance with latest typing spec. This addresses #7848.
@erictraut erictraut mentioned this issue May 7, 2024
Merged
erictraut added a commit that referenced this issue May 7, 2024
@erictraut
Changed interpretation of function definitions with (*args: Any, **kw…
c49af8f 
…args: Any) to be `...` in compliance with latest typing spec. This addresses #7848. (#7859)
@erictraut erictraut added the addressed in next version Issue is fixed and will appear in next published version label May 7, 2024
@erictraut
Copy link
Collaborator Author

This is addressed in pyright 1.1.362, which I just published.

@Viicos Viicos mentioned this issue May 29, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
addressed in next version Issue is fixed and will appear in next published version bug Something isn't working spec compliance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@erictraut