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

2014年2月14日 09:22:44 -0800

On Fri, Feb 14, 2014 at 2:42 AM, Nick Coghlan <[email protected]> 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
support)
But do you do that with a generic type or a special one for each type?
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
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
[email protected]
_______________________________________________
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to