[Python-Dev] Is static typing still optional? (original) (raw)
Chris Barker - NOAA Federal chris.barker at noaa.gov
Mon Dec 11 12:10:57 EST 2017
- Previous message (by thread): [Python-Dev] Is static typing still optional?
- Next message (by thread): [Python-Dev] Is static typing still optional?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
.
I see a couple of options: 1a: Use a default type annotation, if one is not is supplied. typing.Any would presumably make the most sense. 1b: Use None if not type is supplied. 2: Rework the code to not require annotations at all.
I think I'd prefer 1a, since it's easy.
- would be great :-)
I find this bit of “typing creep” makes me nervous— Typing should Never be required!
I understand that the intent here is that the user could ignore typing and have it all still work. But I’d rather is was not still there under the hood.
Just because standardized way to do something is included in core Python doesn’t mean the standard library has to use it.
However, typing is not currently imported by dataclasses.py.
And there you have an actual reason besides my uneasiness :-)
- CHB -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171211/4059d471/attachment.html>
- Previous message (by thread): [Python-Dev] Is static typing still optional?
- Next message (by thread): [Python-Dev] Is static typing still optional?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]