Title: Specify how type checkers should interpret `__exit__` annotations · Issue #1535 · python/typing · GitHub
Open Graph Title: Specify how type checkers should interpret `__exit__` annotations · Issue #1535 · python/typing
X Title: Specify how type checkers should interpret `__exit__` annotations · Issue #1535 · python/typing
Description: The typing spec should provide guidance on how type checkers should handle __exit__ annotations. This method is special because __exit__ methods can suppress exceptions, and whether or not they do so affects the control flow through a fu...
Open Graph Description: The typing spec should provide guidance on how type checkers should handle __exit__ annotations. This method is special because __exit__ methods can suppress exceptions, and whether or not they do ...
X Description: The typing spec should provide guidance on how type checkers should handle __exit__ annotations. This method is special because __exit__ methods can suppress exceptions, and whether or not they do ...
Opengraph URL: https://github.com/python/typing/issues/1535
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Specify how type checkers should interpret `__exit__` annotations","articleBody":"The typing spec should provide guidance on how type checkers should handle `__exit__` annotations. This method is special because `__exit__` methods can suppress exceptions, and whether or not they do so affects the control flow through a function.\r\n\r\nIn code like this:\r\n\r\n```python\r\na: int | None = None\r\nwith some_context():\r\n a = 1\r\nreveal_type(a)\r\n```\r\nWhat is the type of `a`? It depends on whether `some_context()` can suppress exceptions or not. Most context managers don't, but in theory they can. A pedantically correct decision might be to assume that they can always suppress exceptions (so `a` might still be `None` in the sample), but that will often lead to a bad user experience.\r\n\r\nMypy currently follows [a heuristic](https://github.com/python/mypy/issues/7214#issuecomment-513618450) I proposed a few years ago. Should we formalize that heuristic into the spec, or something else?\r\n\r\nThis is important to specify because it affects how library authors should annotate their `__exit__` methods. I'll probably pursue getting this into the spec in the next few months.\r\n\r\n","author":{"url":"https://github.com/JelleZijlstra","@type":"Person","name":"JelleZijlstra"},"datePublished":"2023-12-11T05:08:20Z","url":"https://github.com/python/typing/issues/1535"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:db15f273-954a-1d4f-9d78-f52a130b21cd |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9020:3EE843:2605754:33F3729:6B00432A |
| html-safe-nonce | 75e3cb588d1eb7fbad8a4e88dbf958daa4a32722873182f06cf87e8aadf66452 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5MDIwOjNFRTg0MzoyNjA1NzU0OjMzRjM3Mjk6NkIwMDQzMkEiLCJ2aXNpdG9yX2lkIjoiNjYxMDMwMTE1Mzk0MDg4MjIxOCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | fca547b94f3f4f69dc1aca6fe939b9b57f94d5b13650956a474563735cb40d2f |
| hovercard-subject-tag | issue:2034841745 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python/typing/1535/issue_layout |
| twitter:image | https://opengraph.githubassets.com/cb055ef1d8da008fe640cfc410978b081f1059dcf04fe1a7cf8f5413083044d6/python/typing/issues/1535 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/cb055ef1d8da008fe640cfc410978b081f1059dcf04fe1a7cf8f5413083044d6/python/typing/issues/1535 |
| og:image:alt | The typing spec should provide guidance on how type checkers should handle __exit__ annotations. This method is special because __exit__ methods can suppress exceptions, and whether or not they do ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | JelleZijlstra |
| hostname | github.com |
| expected-hostname | github.com |
| None | 7d0829bbde9e48b2486cb5dd6d147896eb01d32134627091f818958a935ef3f0 |
| turbo-cache-control | no-preview |
| go-import | github.com/python/typing git https://github.com/python/typing.git |
| octolytics-dimension-user_id | 1525981 |
| octolytics-dimension-user_login | python |
| octolytics-dimension-repository_id | 24604008 |
| octolytics-dimension-repository_nwo | python/typing |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 24604008 |
| octolytics-dimension-repository_network_root_nwo | python/typing |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | f3f3a43ca095cdea3abbb394112e971f9fdb94fa |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width