Mark Dickinson <dicki...@gmail.com> added the comment: Issue 1: (passing coefficients to decimal constructor): While I agree that passing a coefficient for an infinity doesn't make a lot of sense, there's a backwards compatibility problem here: it worked in 3.1, so making it raise an exception in 3.2 might break code. However, it seems unlikely that there's any correct code out there that's passing a coefficient other than (0,) or () for an infinity, so I'd be prepared to make this an error for coefficients other than () and (0,).
Issue 2: (inf.as_tuple() returns () instead of (0,) for coefficient). On balance I'd prefer to leave this as it is. It's a minor inconsistency, but I don't think it really does any harm. Unless there's a real bug, making a minor change like this to an established API seems more likely to do harm than good. (It could break docstrings in third-party packages, for example.) ---------- nosy: +rhettinger versions: +Python 2.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7684> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
