Skip to content
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.

Behavior of __exit__ #11

Closed
JelleZijlstra opened this issue Nov 23, 2023 · 1 comment
Closed

Behavior of __exit__ #11

JelleZijlstra opened this issue Nov 23, 2023 · 1 comment
Labels
wait-for-council Issues that should not be addressed until the Typing Council exists

Comments

@JelleZijlstra
Copy link
Owner

The spec should provide guidance on how type checkers should handle __exit__ annotations. Mypy currently follows a heuristic I proposed a few years ago. Should we formalize that heuristic into the spec, or something else?

This is important to specify because it affects how library authors should annotate their __exit__ methods.
@JelleZijlstra JelleZijlstra added the wait-for-council Issues that should not be addressed until the Typing Council exists label Nov 23, 2023
@JelleZijlstra
Copy link
Owner Author

python/typing#1535

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
wait-for-council Issues that should not be addressed until the Typing Council exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JelleZijlstra