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 cdavid
Recipients cdavid, christian.heimes, mark.dickinson, rhettinger
Date 2009-01-06.13:16:41
SpamBayes Score 0.09072388
Marked as misclassified No
Message-id <1231247802.46.0.346574528499.issue2121@psf.upfronthosting.co.za>
In-reply-to
Content
> I disagree. *Why* do you think it should work?  It fails for many other 
> types:

I don't understand the rationale: why not making something work better
if possible ? Also, I don't understand the comparison with Decimal or
Fraction; there is a big difference between making the roundtrip not
possible at all for a type, and making it possible only for some values.

> I think the *right* solution is to define repr of a complex number
> z to be:

Why ? I don't understand those examples: maybe I am missing your
argument, but I understand it as we should not fix one bug because there
are another bugs related to inf and nan in complex. For me, something like:

a = complex(0)
a *= float('inf') * 1j
-> a = nan+nanj

Is really not desirable. That's actually a more serious bug than this
one. Are you saying that python does not care about inf/nan for complex
numbers ? If so, be it, but it would a bit unfortunate.
History
Date User Action Args
2009-01-06 13:16:42cdavidsetrecipients: + cdavid, rhettinger, mark.dickinson, christian.heimes
2009-01-06 13:16:42cdavidsetmessageid: <1231247802.46.0.346574528499.issue2121@psf.upfronthosting.co.za>
2009-01-06 13:16:41cdavidlinkissue2121 messages
2009-01-06 13:16:41cdavidcreate