On Tue, 9 Nov 2021 at 10:39, Sebastian Rittau <srit...@rittau.biz> wrote:
> This might be better API design (although I don't think Python should be > opinionated about this outside the standard library), but this still > leaves the API change example and the very real problem of @overloads > unsolved. You can handle this using *args and/or **kwargs, so Python does support this API design if you want to use it. I disagree, however, with the statement that Python shouldn't be "opinionated" about this. It's not a matter of being opinionated, IMO, it's about whether Python has to have explicit language support for every possible use case that anyone comes up with. In this case, the situation seems rare enough, and the API design is sufficiently unusual (which is a polite way of me saying that I think it's a bad design...), that I think it's entirely reasonable for Python to not support it outside of the generic *args/**kwargs machinery. 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/YO35XE6JHYNGQ4JHX3ZI4YBKXJ5XTG4O/ Code of Conduct: http://python.org/psf/codeofconduct/
