On 30/09/2018 15:48, Chris Angelico wrote: > On Mon, Oct 1, 2018 at 12:45 AM Anders Hovmöller <bo...@killingar.net> wrote: >> But making any change to the basic types truth table is a big -1 from me. >> This seems like a Python 2-3 transition to me. >> > > Far FAR worse than anything that changed in Py2->Py3. > > ChrisA > _______________________________________________ > Python-ideas mailing list > Python-ideas@python.org > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/ > I can see that breaking a LOT of existing code so would not think that it would be a practical option, I am thinking of having a isnan &/or isvalue.
If the behaviour of integers were changed so that all NaN producing operations that took non-NaN inputs were to produce a signalling NaN, i.e. also produce an Exception but a pass on that Exception (explicitly changed Signalling NaN to Quiet NaN) I don't see any non-NaN aware code being forced to change. -- Steve (Gadget) Barnes Any opinions in this message are my personal opinions and do not reflect those of my employer. --- This email has been checked for viruses by AVG. https://www.avg.com _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
