Mark Dickinson [EMAIL PROTECTED] added the comment:
Merged to 2.6 and 3.0 maintenance branches (r67700, r67701).
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4084
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Unless Facundo or some of the other decimal contributors reviews and
applies this patch really quickly, it is out of scope for 2.5.3.
--
nosy: +loewis
___
Python tracker [EMAIL PROTECTED]
Facundo Batista [EMAIL PROTECTED] added the comment:
Commited in trunk and Py3, thanks Mark!
Please, could you commit it in 2.5? The only change I've made in the
patch is adding the issue number to Misc/NEWS, the rest is ok.
After that, just close this.
Thanks again!
--
versions:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Mark, if you want to backport this, please go ahead. If want me to,
assign to me.
--
assignee: facundobatista - marketdickinson
priority: normal - release blocker
___
Python tracker [EMAIL
Changes by Mark Dickinson [EMAIL PROTECTED]:
--
versions: +Python 3.1
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4084
___
___
Python-bugs-list
New submission from Mark Dickinson [EMAIL PROTECTED]:
Here's a snippet from Python 2.6:
from decimal import Decimal, getcontext
getcontext().prec = 3
Decimal('NaN').max(Decimal('1234'))
Decimal('sNaN234')
The result here should be Decimal('1.23E+3')---the specification says that
the result
