On Fri, 1 Oct 2021 at 15:50, Christopher Barker <python...@gmail.com> wrote: > > The fact that the built in “any” is not a type is not an implementation > detail. any() and typing.Any are completely different things/concepts. They > just happen to be spelled the same.
Agreed. > I don’t think it’s a bad thing that objects that are specifically about Type > Hinting can be found in the typing module. > > Overloading names in builtins to save an import is a really bad idea. Having to take the runtime cost of an import to do a development-time static analysis of the code, sort of is, though... Paul _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/43ML2YGBXUR5OHKQKPNJNFUB3X6J34LE/ Code of Conduct: http://python.org/psf/codeofconduct/
