Message 136468 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	mark.dickinson
Recipients	alex, belopolsky, daniel.urban, mark.dickinson, pitrou, rhettinger
Date	2011-05-21.19:32:27
SpamBayes Score	9.7635975e-06
Marked as misclassified	No
Message-id	<1306006347.99.0.00190259995193.issue11986@psf.upfronthosting.co.za>
In-reply-to

Content
> keep naive implementation of builtin max() Agreed. > provide symmetric float.max such that nan.max(x) = x.max(nan) = x (nan > result would be a valid but less useful alternative.) That might be viable (a math module function might also make sense here), though it feels a bit YAGNI to me. If we were going to add such a method, it should follow IEEE 754: nan.max(x) == x.max(n) == x, but also nan.min(x) == x.min(nan) == x, for finite x. (See section 5.3.1.)

> keep naive implementation of builtin max()

Agreed.

> provide symmetric float.max such that nan.max(x) = x.max(nan) = x (nan
> result would be a valid but less useful alternative.)

That might be viable (a math module function might also make sense here), though it feels a bit YAGNI to me.  If we were going to add such a method, it should follow IEEE 754:  nan.max(x) == x.max(n) == x, but also nan.min(x) == x.min(nan) == x, for finite x.  (See section 5.3.1.)

History
Date	User	Action	Args
2011-05-21 19:32:28	mark.dickinson	set	recipients: + mark.dickinson, rhettinger, belopolsky, pitrou, alex, daniel.urban
2011-05-21 19:32:27	mark.dickinson	set	messageid: <1306006347.99.0.00190259995193.issue11986@psf.upfronthosting.co.za>
2011-05-21 19:32:27	mark.dickinson	link	issue11986 messages
2011-05-21 19:32:27	mark.dickinson	create