Showing content from http://mail.python.org/pipermail/python-dev/attachments/20170528/1685146e/attachment.html below:
<div dir="ltr">Thanks everyone for interesting suggestions!<br><div><br>@Antoine @Guido:<br></div><div>Some of the possible options for the title are:<br></div><div>* Protocols (structural subtyping)<br></div><div>* Protocols (static duck typing)<br></div><div>* Structural subtyping (static duck typing)<br></div><div>which one do you prefer?<br><br></div><div>@Nick:<br></div><div>Yes, explicit imports are not necessary for static type checkers (I will add a short comment about this).<br><br></div><div>@Mark:<br></div><div>I agree with Guido on all points here. For example, collections.abc.Iterable is already a class,<br>and lots of code uses isinstance(obj, collections.abc.Iterable) and similar checks with other ABCs<br>(also in a structural manner, i.e. via __subclasshook__). So that disabling this will case many breakages.<br>The question of whether typing.Iterable[int] should be a class is independent (orthogonal) and<br>does not belong to this PEP.<br><br>--<br></div><div>Ivan<br><br><br></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4