On Tue, 30 Nov 2021 at 12:39, Oscar Benjamin <oscar.j.benja...@gmail.com> wrote:
> There are other open "issues" like this for SymPy where the > presumption is that not having type hints is now to be considered a > deficiency of the library regardless of whether the hints have any > benefit for internal use. I don't object to adding the hints but it's > a huge amount of work that someone would have to do and I don't want > to add useless/inaccurate hints temporarily (as some have suggested to > do). This is precisely the sort of concern I have. Although it is awfully tempting to passive-aggressively annotate everything as Any, just to shut people up :-( And to be clear, it's often very non-obvious how to annotate something - in https://github.com/pfmoore/editables I basically gave up because I couldn't work out how to write a maintainable annotation for an argument that is "a Path, or something that can be passed to the Path constructor to create a Path" (it's essentially impossible without copy/pasting the argument annotation for the Path constructor). I also spent a lot of time trying to deal with a typeshed bug. And even worse, if I put the types in a .pyi file (which I want to do, because I don't want the library to import typing at runtime because it's a significant overhead for something that's supposed to be lightweight), apparently mypy won't check them so I gain no benefit for the project itself. Anyway, we're *way* off topic now, and I doubt there's much that the SC or python-dev can do to change the community view on typing, anyway. Paul _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/4DUJM7MNJSJ3TOYYFILQCG4RT4CU6DME/ Code of Conduct: http://python.org/psf/codeofconduct/
