[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Ned Deily added the comment: As far as I can tell, the only places that typing was declared as provisional were in PEP 484 and twice in the 3.5 What's New document (https://docs.python.org/3.5/whatsnew/3.5.html); it doesn't appear to have been mentioned in the library reference

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Brett Cannon added the comment: Keeping it provisional sounds reasonable to me, especially if it helps land protocol support. -- nosy: +brett.cannon ___ Python tracker

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Raymond Hettinger added the comment: +1 for keeping this provisional. The code is still maturing and needs to be iterated while we gain experience with it. -- nosy: +rhettinger ___ Python tracker

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Changes by Berker Peksag : -- nosy: +ned.deily ___ Python tracker ___ ___

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Ivan Levkivskyi added the comment: There are also minor things like NoReturn, typing_inspect helpers(?) etc. The main good point I see for keeping typing provisional is we could iterate fast and come up with more "settled" and robust API in time for 3.7. --

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Łukasz Langa added the comment: There are three specific areas I can identify that are missing from the typing module at the moment: * support for structural typing (protocols) * support for typing heterogenous dictionaries (dictionary "schema") * support for typing arbitrary callables

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

Ivan Levkivskyi added the comment: I don't have any strong opinion on this. If others don't object then I am perfectly fine with keeping typing provisional for 3.6. -- nosy: +levkivskyi ___ Python tracker

[issue29316] Can we keep typing.py provisional for the duration of the Python 3.6 release cycle?

New submission from Guido van Rossum: The 3.6 what's new (https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-typing) claims typing.py is no longer provisional, but I don't think it's quite ready yet. There are a number of things that I'd like to merge into typing.py over the duration of