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

[Ned Deily]

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 
(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.

--
stage:  -> needs patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Brett Cannon]

Brett Cannon added the comment:

Keeping it provisional sounds reasonable to me, especially if it helps land 
protocol support.

--
nosy: +brett.cannon

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raymond Hettinger]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Berker Peksag]

Changes by Berker Peksag :


--
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Ivan Levkivskyi]

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Łukasz Langa]

Ł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

--
components: +Library (Lib)
keywords: +3.6regression
nosy: +lukasz.langa
versions: +Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Ivan Levkivskyi]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Guido van Rossum]

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 3.6's lifetime. Nothing backwards incompatible, but definitely new 
features.

See also https://github.com/python/typing/issues/247

--
messages: 285758
nosy: gvanrossum
priority: normal
severity: normal
status: open
title: Can we keep typing.py provisional for the duration of the Python 3.6 
release cycle?

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com