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 eric.smith
Recipients ajaksu2, eric.smith, gvanrossum, mark, mark.dickinson
Date 2009-04-27.09:10:13
SpamBayes Score 0.00040065916
Marked as misclassified No
Message-id <1240823444.14.0.840481206924.issue1588@psf.upfronthosting.co.za>
In-reply-to
Content
I agree this is a feature request. It comes down to:

What should the format specifier mini-language for complex numbers look
like?

Should it look like the existing mini-language for floats, but have the
format specified twice, with some sort of delimiter? Or just specified
once, and use that for both parts?

I'm sure python-ideas could argue over it for ages, but I don't see any
outcome that's much of an improvement over the suggested:
"{0.real:.5f}{0.imag:+.5f}j".format(complex(1, -2/3))
History
Date User Action Args
2009-04-27 09:10:54eric.smithsetrecipients: + eric.smith, gvanrossum, mark.dickinson, ajaksu2, mark
2009-04-27 09:10:44eric.smithsetmessageid: <1240823444.14.0.840481206924.issue1588@psf.upfronthosting.co.za>
2009-04-27 09:10:36eric.smithlinkissue1588 messages
2009-04-27 09:10:18eric.smithcreate