Not defining the semantics of annotations was a brave move, but inevitably led to the situation where different use cases, all quite reasonable, would spring into being. Now they have, the development team has to decide a) which ones to sanction and b) which will be left out in the cold.
I wish them well. Kind regards, Steve On Wed, Mar 30, 2022 at 5:24 PM Christopher Barker <[email protected]> wrote: > > I personally would love for a typing.python.org or equivalent > subsection of docs.python.org to exist. > > +1 > > There’s a wrinkle here, however. The type specs are Python, but how they > are used/interpreted is up to third party packages. > > So it’s a bit tricky to know exactly what to document where. > > I don’t think that’s insurmountable, but something to keep in mind. > > For example, while the clear specs are the first step, what the community > really could use is a good “recommended practices for static typing” doc — > and that’s harder to do without reference to particular tools. > > -CHB > > > -- > Christopher Barker, PhD (Chris) > > Python Language Consulting > - Teaching > - Scientific Software Development > - Desktop GUI and Web Development > - wxPython, numpy, scipy, Cython > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/YF5UIQIWNVIANFOCIQ2J4DJACQGJDGVM/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/NW3SRUA2H3KNZBD4CICXY5QF2YWELUV5/ Code of Conduct: http://python.org/psf/codeofconduct/
