➜

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 eli.bendersky
Recipients barry, eli.bendersky, eric.smith, ethan.furman, serhiy.storchaka
Date 2013-08-14.20:04:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAF-Rda8XUs=Td7Xkqk-opWrWGd=aoYz1e-F3R6ybfxurdg6S-g@mail.gmail.com>
In-reply-to <1376509321.25.0.31196418024.issue18738@psf.upfronthosting.co.za>
Content 
>
> Okay, I see your points.  I can certainly agree with going with the str
> representation when no numeric code is specified.  But, if a numeric code
> is specified (x, b, d, etc.) then the numeric value should be used.
>
> Agreed?
>

 Yes. I suggest to wait a day or two for others to react (night in Europe,
etc). If this sounds good to everyone then it may make sense to split this
issue to one for str.format and another for legacy % formatting, because
the implementation is likely to be different.
History
Date User Action Args
2013-08-14 20:04:22eli.benderskysetrecipients: + eli.bendersky, barry, eric.smith, ethan.furman, serhiy.storchaka
2013-08-14 20:04:22eli.benderskylinkissue18738 messages
2013-08-14 20:04:22eli.benderskycreate