On Thu, 11 Nov 2021 at 22:22, Brendan Barnwell <brenb...@brenbarn.net> wrote: > > On 2021-11-11 09:33, Paul Moore wrote: > > I understand that. However, PEP 8 states "Names that are visible to > > the user as public parts of the API should > > follow conventions that reflect*usage* rather than*implementation*." > > (My emphasis) I quoted this, but you cut that part of my post. > > I'm not the one who previously replied to your earlier post, but I > still don't really understand what the relevance of this is. EVERY > class can be used like a function (barring perhaps a few oddities like > None). So the fact that you see a name used like `str(this)` or > `list(that)` or `some_name(a, b, c)` doesn't tell you anything about > "usage". That syntax is completely consistent with usage as a class and > as a function.
Chris Angelico made the point far better than I've managed to, and in any case the thread is basically finished at this point, so I won't say anything more other than to quote Chris and say "this is what I was trying to say": > The distinction between "this is a type" and "this is a function" is > often relatively insignificant. The crux of your proposal is that it > should be more significant, and that the fundamental APIs of various > core Python callables should reflect this distinction. This is a lot > of churn and only a philosophical advantage, not a practical one. 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/X7AV7WMDISAZSADHQT7XJ3AFYIMGD5TE/ Code of Conduct: http://python.org/psf/codeofconduct/
