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 ajaksu2, eric.smith, gvanrossum, mark, mark.dickinson
Date 2009-04-27.09:26:20
SpamBayes Score 1.7607452e-07
Marked as misclassified No
Message-id <1240824417.5.0.45996170058.issue1588@psf.upfronthosting.co.za>
In-reply-to
Content
> 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?

This sounds clumsy to me.  I'd guess that in most uses you'd want the
same format for both pieces.

> Or just specified once, and use that for both parts?

That doesn't sound unreasonable.  But there might need to be some
thinking about exactly what a '+' modifier means, or how you pad with
zeros on the left when you've got two pieces to pad.

It seems simplest just to tell people to format the real and imaginary
parts by hand.  As it isn't totally obvious how to do this (e.g.,
remembering the '+' for the imaginary part), perhaps there should be a
recipe in the docs somewhere?
History
Date User Action Args
2009-04-27 09:27:07mark.dickinsonsetrecipients: + mark.dickinson, gvanrossum, eric.smith, ajaksu2, mark
2009-04-27 09:26:57mark.dickinsonsetmessageid: <1240824417.5.0.45996170058.issue1588@psf.upfronthosting.co.za>
2009-04-27 09:26:51mark.dickinsonlinkissue1588 messages
2009-04-27 09:26:32mark.dickinsoncreate