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.

Title: Complex representation
Type: Stage:
Components: Interpreter Core Versions: Python 2.6
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: collinwinter Nosy List: collinwinter, hwundram, sonderblade, terry.reedy
Priority: normal Keywords: patch

Created on 2006-05-19 21:27 by hwundram, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
python-complex.diff hwundram, 2006-05-20 11:20 Complex constructor patch to accept bracketed values.
Messages (7)
msg50297 - (view) Author: Heiko Wundram (hwundram) Date: 2006-05-19 21:27
As per request on c.l.p:

I've implemented a small patch to change the output of
repr(x) for complex variables, so that complex(repr(x))
works for any complex x. This changes the output of
repr(x) to


without brackets, but leaves the string output
untouched. This change of behaviour would be in line
with int(repr(x)) and float(repr(x)) being defined for
any int or float x, repectively.

I don't know whether this patch is sensible, and
whether it breaks any current code, because (for example)

eval("5*%r" % (1+2j,))

won't work properly anymore, or whether it'd be more
sensible to change the complex constructor to also
accept a bracketed expression. I'll attach a patch to
do the latter later.
msg50298 - (view) Author: Heiko Wundram (hwundram) Date: 2006-05-19 22:28
Logged In: YES 

The second patch (python-complex-constructor.diff) changes
the constructor to accept bracketed complex numbers which
are enclosed in a single bracket. I'd rather say this is the
better appropach to have complex(repr(x)) work, but I leave
both patches attached to this bug.

The latter patch also creates test cases testing for
formatting errors with bracketed expressions.
msg50299 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2006-05-20 05:24
Logged In: YES 

(The current behavior is not a bug, nor is this patch 
submission a bug report, so let us omit that word.)
I think your example suggests why complexes are printed in 
parens, so I think enhancing complex() to accept such is 
the better approach if any change is to be made.
msg50300 - (view) Author: Heiko Wundram (hwundram) Date: 2006-05-20 11:20
Logged In: YES 

The attached patch is a revised version of the patch to the
complex constructor to accept bracketed string expressions,
which also adds documentation changes (whatsnew25).

Anyway, I personally also find this to be the "better" way,
so I've removed the repr-changing patch. And, calling it a
bug was by accident: I should've rather called it tracker
item, which is pretty synonymous for me.
msg50301 - (view) Author: Björn Lindqvist (sonderblade) Date: 2007-03-08 00:04
I have applied this patch in 2.6 and it seem to work as intended. The unit tests all pass. I guess the change could be useful if you are are serializing and desearializing lists of complex numbers. I think it should be applied.
msg50302 - (view) Author: Collin Winter (collinwinter) * (Python committer) Date: 2007-03-08 19:09
Works for me. I'll commit this for 2.6 (no backport) if there are no objections.
msg50303 - (view) Author: Collin Winter (collinwinter) * (Python committer) Date: 2007-03-09 20:33
Applied as r54247. Thanks for your patch!
Date User Action Args
2022-04-11 14:56:17adminsetgithub: 43383
2006-05-19 21:27:31hwundramcreate