Message98531
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.) |
|
Date |
User |
Action |
Args |
2010-01-29 19:30:59 | mark.dickinson | set | recipients:
+ mark.dickinson, rhettinger, skrah |
2010-01-29 19:30:59 | mark.dickinson | set | messageid: <1264793459.37.0.767150182776.issue7684@psf.upfronthosting.co.za> |
2010-01-29 19:30:58 | mark.dickinson | link | issue7684 messages |
2010-01-29 19:30:57 | mark.dickinson | create | |
|