[Python-Dev] return type of __complex__

Tres Seaver tseaver at palladion.com
Fri Oct 19 18:44:23 CEST 2012


-----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'.

> 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.


Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCBg2cACgkQ+gerLs4ltQ5SMACfbhAMwQCwkZi1dF4WGL9uZoeR
wv4AoII2FVW8TPchCcmsh3llo7QPxroW
=gqkG
-----END PGP SIGNATURE-----



More information about the Python-Dev mailing list