Showing content from http://mail.python.org/pipermail/python-dev/attachments/20150420/e4536d2c/attachment.html below:
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Apr 20, 2015 at 2:01 PM, Robert Collins <span dir="ltr"><<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</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 21 April 2015 at 08:50, Harry Percival <<a href="mailto:harry.percival@gmail.com">harry.percival@gmail.com</a>> wrote:<br>
>> stub files are only used to type-check *users* of a module. If you want a<br>
>> module itself to be type-checked you have to use inline type hints<br>
><br>
> is this a fundamental limitation, or just the current state of tooling?<br>
<br>
</span>AIUI its the fundamental design. Stubs don't annotate python code,<br>
they *are* annotated code themselves. They aren't merged with the<br>
observed code at all.<br>
<br>
Could they be? Possibly. I don't know how much work that would be.<span class=""></span><br></blockquote></div><br></div><div class="gmail_extra">It's fundamental in the implementation of mypy. It doesn't have to be in the implementation of other type checkers (and IIRC the Google folks are planning to merge the two streams). However if you are using typing.get_type_hints(func) this is not intended to give you access to hints defined in stubs (it would require a huge amount of machinery to implement that right).<br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature">--Guido van Rossum (<a href="http://python.org/~guido" target="_blank">python.org/~guido</a>)</div>
</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