Update mypy roadmap #3970
Update mypy roadmap #3970
Conversation
| @@ -9,28 +9,16 @@ core team member that nobody else is working on the same thing. | |||
| on, and everything is subject to change. Near-term plans are likely | |||
| more accurate. | |||
|
|
|||
| ## July-December 2017 | |||
| ## September-December 2017 | |||
|
|
|||
| - Fix remaining highest-priority TypedDict issues and make TypedDict | |||
| an officially supported mypy feature. | |||
There was a problem hiding this comment.
When it is planned to move TypedDict to typing? There are still some bugs with TypedDict, but it seems to be "feature complete".
There was a problem hiding this comment.
If you want this in Python 3.7 there should be a PEP (since it is a significant feature). But I think it's better to keep it in typing_extensions, so we can iterate on the feature more quickly. E.g. maybe we end up needing per-field flags for totality.
There was a problem hiding this comment.
But I think it's better to keep it in typing_extensions
It is currently only in mypy_extensions (as well as extended Callable arguments). Maybe it actually makes sense to move these to typing_extensions?
There was a problem hiding this comment.
We should probably debate that on the typing tracker. The difference between the two is that things in mypy_extensions can be unilaterally added or changed by the mypy team, and may forever remain mypy-specific, while things in typing_extensions need to be debated with the other projects using PEP 484 (e.g. PyCharm and pytype) and must be intended for eventual inclusion in typing.py.
No description provided.