<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Nov 3, 2017 at 7:45 AM, Chris Angelico <span dir="ltr"><<a href="mailto:rosuav@gmail.com" target="_blank">rosuav@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sat, Nov 4, 2017 at 1:35 AM, Guido van Rossum <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:<br>
> [A copy from <a href="https://github.com/python/typing/issues/495" rel="noreferrer" target="_blank">https://github.com/python/<wbr>typing/issues/495</a> to get more<br>
> people's attention to this issue.]<br>
><br>
> I'm wondering if we should remove typing from the stdlib. Now's the time to<br>
> think about this, as the feature freeze for 3.7 is about 12 weeks away.<br>
><br>
> Cons:<br>
><br>
> People have to depend on a PyPI package to use typing (but they do anyway<br>
> for typing_extensions)<br>
<br>
</span>If the lazy evaluation of annotations (PEP 563) also lands in 3.7,<br>
then this would be a very minor downside. You'd need to pip-install<br>
typing as well as mypy *for the actual type checking*, but at run<br>
time, you could ignore both (all those List[...] annotations would be<br>
stored unevaluated). Otherwise, it'd mean that any project that makes<br>
use of type hints would require typing as a run-time dependency.<br></blockquote></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">This would not work if you use TypeVar, NewType, or any kind of type alias involving things imported from typing (e.g. Union or TypedDict). Also cast().<br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">--Guido van Rossum (<a href="http://python.org/~guido" target="_blank">python.org/~guido</a>)</div>
</div></div>