> On 10 Nov, 2017, at 4:48 PM, Guido van Rossum <guido at python.org> wrote: > > On Fri, Nov 10, 2017 at 1:20 AM, Lukasz Langa <lukasz at langa.pl <mailto:lukasz at langa.pl>> wrote: > Alright, we're on bikeshed territory now. Finally! :-) > > I was always thinking about this as "static annotations". The fact they're strings at runtime is irrelevant for most people who will use this future. They don't want string annotations, they want them to not be evaluated on import time... they want them to be static. Also, "static typing" et al. I think it has a nice vibe to it. > > I admit "annotations" is too broad but "static_annotations" (or "string_annotations" ¯\_(ツ)_/¯ ) will be the longest __future__ name so far. That was my main motivation behind using the shorter name. And a bit of megalomania I guess. > > I don't mind the long name. Of all the options so far I really only like 'string_annotations' so let's go with that. Done. - Ł -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171110/0fa03e64/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: <http://mail.python.org/pipermail/python-dev/attachments/20171110/0fa03e64/attachment.sig>
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