Mark Dickinson dicki...@gmail.com added the comment:
Thanks, Eric. Committed in r72803; backported to trunk in r72805.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5829
Eric Smith e...@trueblade.com added the comment:
It looks good to me.
--
nosy: +eric.smith
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5829
___
Mark Dickinson dicki...@gmail.com added the comment:
Patch against py3k. If someone can review this I'll apply
it for 3.1; otherwise, it can wait until 3.2.
--
keywords: +patch
priority: - normal
stage: test needed - commit review
versions: -Python 2.6, Python 3.0
Added file:
Changes by Mark Dickinson dicki...@gmail.com:
--
components: +Interpreter Core
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5829
___
___
Changes by Mark Dickinson dicki...@gmail.com:
--
assignee: - marketdickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5829
___
___
Mark Dickinson dicki...@gmail.com added the comment:
complex('1e-500') bug fixed in r71891 (2.6) and r71892 (3.0).
It's already gone in trunk and py3k.
What's left is deciding whether the OverflowError that 2.7 and 3.1
currently produce should disappear in favour of producing infinities
New submission from Mark Dickinson dicki...@gmail.com:
In (for example) Python 2.6:
float('1e500')
inf
complex('1e500')
Traceback (most recent call last):
File stdin, line 1, in module
ValueError: float() out of range: 1e500
I'd say that one of these is a bug, but I'm not sure which one.
Changes by Mark Dickinson dicki...@gmail.com:
--
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5829
___
___
Python-bugs-list
Mark Dickinson dicki...@gmail.com added the comment:
Note: complex('1e-500') also produces ValueError in 2.6. That's
definitely a bug.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5829
