Title: How to handle typechecker specific bugs · Issue #8403 · python/typeshed · GitHub
Open Graph Title: How to handle typechecker specific bugs · Issue #8403 · python/typeshed
X Title: How to handle typechecker specific bugs · Issue #8403 · python/typeshed
Description: In the past, we've worked around typechecker bugs and missing features in typeshed. But as the amount of typecheckers grows and type stubs are used for more that just type checking, I don't think we can work around any bug or missing fea...
Open Graph Description: In the past, we've worked around typechecker bugs and missing features in typeshed. But as the amount of typecheckers grows and type stubs are used for more that just type checking, I don't think w...
X Description: In the past, we've worked around typechecker bugs and missing features in typeshed. But as the amount of typecheckers grows and type stubs are used for more that just type checking, I don't...
Opengraph URL: https://github.com/python/typeshed/issues/8403
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"How to handle typechecker specific bugs","articleBody":"In the past, we've worked around typechecker bugs and missing features in typeshed. But as the amount of typecheckers grows and type stubs are used for more that just type checking, I don't think we can work around any bug or missing feature of every typechecker in typeshed, especially if this means regressing our stubs. Not only is this more maintainer work and it gets hard to remember which typechecker has which bug, it also means that users of bug-free typecheckers and other software will still be affected by those bugs.\r\n\r\nI think that we should still accommodate very impactful bugs and missing major features (per our \"tracking\" bugs) for the \"big four\" mypy, pytype, pyright, and pyre. We also need to work around some bugs due to our tests. But apart from that, we should work with typecheck authors (and there is some overlap here, of course) to come up with a solution.\r\n\r\nRegarding stdlib stubs, I believe one option is that typecheckers ship with a customized version of typeshed for major problems. Apart from that, it's always possible for users to `# type: ignore` a problem with a specific typechecker.","author":{"url":"https://github.com/srittau","@type":"Person","name":"srittau"},"datePublished":"2022-07-26T08:56:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/8403/typeshed/issues/8403"}
| 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:d19a8c83-78da-6835-5280-e15de2981789 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | EBEE:275214:E9E14:151663:6A6362AC |
| html-safe-nonce | d606cf0db5f4f3805d83c734acc566dde5eadd9e3d0d4eb156ed90478659a046 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFQkVFOjI3NTIxNDpFOUUxNDoxNTE2NjM6NkE2MzYyQUMiLCJ2aXNpdG9yX2lkIjoiNDA2ODA4MDAyODI2MTUwNzc1NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 981ee1812486939f2ac5f8625f13e69a64478416f3810d574de30bc788204000 |
| hovercard-subject-tag | issue:1317917155 |
| 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/typeshed/8403/issue_layout |
| twitter:image | https://opengraph.githubassets.com/9b1dd32b7c3939c4d2040b047ccaaf4e66b3bc2a8d0c0b0cc9ca62f22018f3b0/python/typeshed/issues/8403 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/9b1dd32b7c3939c4d2040b047ccaaf4e66b3bc2a8d0c0b0cc9ca62f22018f3b0/python/typeshed/issues/8403 |
| og:image:alt | In the past, we've worked around typechecker bugs and missing features in typeshed. But as the amount of typecheckers grows and type stubs are used for more that just type checking, I don't think w... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | srittau |
| hostname | github.com |
| expected-hostname | github.com |
| None | 669d3fcd704a169521d2b6431762f95a6878a9e8ccaf0fd5f2d0802fc5b971f9 |
| turbo-cache-control | no-preview |
| go-import | github.com/python/typeshed git https://github.com/python/typeshed.git |
| octolytics-dimension-user_id | 1525981 |
| octolytics-dimension-user_login | python |
| octolytics-dimension-repository_id | 31696383 |
| octolytics-dimension-repository_nwo | python/typeshed |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 31696383 |
| octolytics-dimension-repository_network_root_nwo | python/typeshed |
| 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 | 20da292f132ff51328be50073854259f417052c1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width