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.16:51:51
SpamBayes Score 1.2902875e-06
Marked as misclassified No
Message-id <1240851112.76.0.198463429929.issue1588@psf.upfronthosting.co.za>
In-reply-to
Content
> How about this:

> - we have a single specifier with the same format as floats
> - we force the sign on the imaginary part to be '+', no
>    matter what was specified
> - we add a 'j' after the imaginary part

This sounds good to me.  I assume a '+' would still affect
the sign of the real part?

> - we ignore any width specified (and therefor any alignment
>    and padding)

I don't see any problem with dealing with width, alignment
and padding with a user-specified fill character;  I think we
should keep these if possible.  It's just zero padding where
it's not clear what should happen.

For the bits that are disabled (e.g., zero padding), should
there be a ValueError raised, or do those bits just get
silently ignored?
History
Date User Action Args
2009-04-27 16:51:53mark.dickinsonsetrecipients: + mark.dickinson, gvanrossum, eric.smith, ajaksu2, mark
2009-04-27 16:51:52mark.dickinsonsetmessageid: <1240851112.76.0.198463429929.issue1588@psf.upfronthosting.co.za>
2009-04-27 16:51:51mark.dickinsonlinkissue1588 messages
2009-04-27 16:51:51mark.dickinsoncreate