[Python-Dev] python 3 niggle: None < 1 raises TypeError

Chris Barker chris.barker at noaa.gov
Fri Feb 14 18:19:55 CET 2014

On Fri, Feb 14, 2014 at 2:42 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

>  That's the main reason I still occasionally wonder if
> "AlwaysMin" and "AlwaysMax" singletons might make sense, although that
> approach has problems of its own (specifically, it's hard to actually
> use without breaking the clean NULL -> None mapping and in many cases
> +/- infinity already work fine).

only for floating point -- it would be nice to have them for other types:
integers,  datetimes, any others that make sense.... ( In know I've wanted
+-inf and NaN for integers forever, though what I really want is hardware

But do you do that with a generic type or a special one for each type?



Christopher Barker, Ph.D.

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140214/79a6b09a/attachment.html>

More information about the Python-Dev mailing list