On 3/18/2010 6:18 PM, Antoine Pitrou wrote:
Glenn Linderman<v+python<at> g.nevcal.com> writes:
On 3/18/2010 2:48 PM, Nick Coghlan wrote:
When there is a clear, correct way (based on Decimal.from_float) to make
numeric comparison behave in accordance with the rules of mathematics,
do we really want to preserve strange, unintuitive behaviour like the above?
I'm aware of nothing that prevents the lazy coder from having a class
unifiedNumber in his toolbox [snip]
Please stick to the topic. We are talking about Python's default behaviour here.
Yes, I consider my comment relevant, and think that you should apologize
for claiming it is off topic.
There are two choices on the table -- doing comparisons implicitly
between Decimal and float, and raising an exception. It seems the
current behavior, sorting by type, is universally disliked, but doing
nothing is a third choice.
So if the default behavior is to raise an exception, my comment pointed
out the way comparisons could be provided, for those that need them.
This allows both behaviors to exist concurrently. Python developers
could even consider including such a library in the standard library,
although my suggestion didn't include that.
On the other hand, if the default behavior is to do an implicit
conversion, I don't know of any way that that could be turned into an
exception for those coders that don't want or don't like the particular
type of implicit conversion chosen.
Glenn
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
