On Mon, Dec 21, 2020 at 3:37 PM Greg Ewing <greg.ew...@canterbury.ac.nz> wrote:
> > However, that ship has sailed. I think it would have been minimally > > disruptive when True and False were first introduced, > > It would have been just as disruptive back then -- that's the > reason bool was made a subclass of int in the first place. > I know why, but I'm not so sure -- no one was using a built in True or False as an integer, because they didn't exist. I suppose folks were using the results of, e.g. `a == b` as an integer, but how often? Where else is an explicit True or False returned by Python itself? But anyway, it would certainly be even more disruptive now. - CHB -- Christopher Barker, PhD Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython
_______________________________________________ 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/WDX5I44P7RCIT6QRKE3TAUUI2A4TRSBJ/ Code of Conduct: http://python.org/psf/codeofconduct/
