[Python-Dev] [OT] Re: Is static typing still optional?

Antoine Pitrou solipsis at pitrou.net
Fri Dec 15 06:04:01 EST 2017


I'm not sure what Mail User Agent each of you is using, but it is quite
impossible (here) to make out who is saying what in your latest
messages.

See plain text rendering here:
https://mail.python.org/pipermail/python-dev/2017-December/151274.html

Regards

Antoine.


On Fri, 15 Dec 2017 10:56:28 +0000
Steve Holden <steve at holdenweb.com> wrote:
> On Mon, Dec 11, 2017 at 5:10 PM, Chris Barker - NOAA Federal <
> chris.barker at noaa.gov> wrote:  
> 
> > .
> >
> > 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.
> >
> >
> > 2) would be great :-)
> >
> > I find this bit of “typing creep” makes me nervous— Typing should Never be
> > required!
> >
> > ​+1  
>> 
> 
> > 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.
> >
> > ​I trust my repetition of the point that the stdlib is an important  
> learning resource isn't unduly harping on the subject. Python is in danger
> of becoming pretty arcane rather too rapidly for my own liking​, though I
> confess to being mostly a consumer of Python.
> 
> > However, typing is not currently imported by dataclasses.py.
> >
> >
> > And there you have an actual reason besides my uneasiness :-)
> >
> > - CHB
> >
> > ​hmm...​  
> 





More information about the Python-Dev mailing list