This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients mark.dickinson
Date 2009-02-10.23:19:21
SpamBayes Score 1.4655474e-09
Marked as misclassified No
Message-id <1234307963.56.0.00813246872741.issue5211@psf.upfronthosting.co.za>
In-reply-to
Content
In the 'coercion rules' section of the reference manual, at:

http://docs.python.org/dev/reference/datamodel.html#id5

it says:

"""Over time, the type complex may be fixed to avoid coercion."""

In 3.x, the complex type has (necessarily) been fixed to avoid coercion, 
and it ought to be a fairly easy task to backport that fix to 2.7, for 
someone who wants to get his or her feet wet with some CPython hacking.

As far as I can see, there's no great benefit in such a change, except 
that the presence of coercion for the complex type causes confusion 
occasionally: see issue 3734 for an example of this.
History
Date User Action Args
2009-02-10 23:19:23mark.dickinsonsetrecipients: + mark.dickinson
2009-02-10 23:19:23mark.dickinsonsetmessageid: <1234307963.56.0.00813246872741.issue5211@psf.upfronthosting.co.za>
2009-02-10 23:19:22mark.dickinsonlinkissue5211 messages
2009-02-10 23:19:21mark.dickinsoncreate