2012/10/19 Tres Seaver <tseaver at palladion.com>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/19/2012 11:56 AM, Benjamin Peterson wrote: >> 2012/10/19 Tres Seaver <tseaver at palladion.com>: >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>> >>> On 10/19/2012 11:26 AM, Benjamin Peterson wrote: >>>> 2012/10/19 Antonio Cuni <anto.cuni at gmail.com>: >>>>> indeed, you are right. So I suppose that in pypy we could just >>>>> relax the check in cmath and be happy. Is there any chance that >>>>> this will be changed in 2.7 and/or 3.x? >>>> >>>> Certainly 3.x, but not 2.7. >>> >>> Why not 2.7? It is a perfectly-backward-compatible change: no >>> currenly-working code could possibly break if cmath's restriction >>> was relaxed. >> >> It's a new feature. > > That is an assertion; I can dqually assert that the current over-strict > typechecking is a bug, because it doesn't conform to the semandics of > 'comples_new'. Nobody claimed it did conform to semantics of complex_new. > >> Also, it's possible that someone is relying on it throwing for >> non-complex values. > > No already working, non-contrived code would break, becuase float is > perfectly-promotable to complex. I'm not saying the code which would break is good, I'm just saying it shouldn't be broken in bugfix releases. -- Regards, Benjamin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4