On Mon, Nov 20, 2017 at 7:58 PM, Lukasz Langa <lukasz at langa.pl> wrote: > I agree with you. The special handling of outermost strings vs. strings > embedded inside annotations bugged me a lot. Now you convinced me that this > functionality should be moved to `get_type_hints()` and the __future__ > import shouldn't try to special-case this one instance, while leaving > others as is. > > > <Python-Dev at python.org> That's better. I don't necessarily care if there will be a warning when a string is given as annotation, but if the idea is to simplify things for the future and get rid of strings to represent types, then this would be a good moment to gently "enforce" it. ––Koos -- + Koos Zevenhoven + http://twitter.com/k7hoven + -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171120/eefc51d9/attachment.html>
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