This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients brett.cannon, gvanrossum, levkivskyi, lukasz.langa, ned.deily, rhettinger
Date 2017-01-19.23:51:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484869890.69.0.394705877071.issue29316@psf.upfronthosting.co.za>
In-reply-to
Content
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 (https://docs.python.org/3.5/library/typing.html) and probably should have been.  FTR, it looks like there was some discussion of removing typing's provisional status in https://github.com/python/typing/issues/278 and https://github.com/python/typing/issues/247.  While it seems somewhat unusual to reinstate a feature's provisional status, I don't have an objection as 3.6 release manager since it is clear that typing is still a new and evolving module.  To make the change in status, the 3.6 What's New document should be updated, a Misc/NEWS entry added for 3.6.1, and the provisional status added to Docs/library/typing.rst.
History
Date User Action Args
2017-01-19 23:51:30ned.deilysetrecipients: + ned.deily, gvanrossum, brett.cannon, rhettinger, lukasz.langa, levkivskyi
2017-01-19 23:51:30ned.deilysetmessageid: <1484869890.69.0.394705877071.issue29316@psf.upfronthosting.co.za>
2017-01-19 23:51:30ned.deilylinkissue29316 messages
2017-01-19 23:51:30ned.deilycreate