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 zach.ware
Recipients Gerrit.Holl, barry, docs@python, georg.brandl, zach.ware
Date 2014-01-20.17:34:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390239284.35.0.828903006004.issue20314@psf.upfronthosting.co.za>
In-reply-to
Content
I would suggest moving the section "4.7.2. printf-style String Formatting" from stdtypes to string, alongside the other two formatting specifications, or otherwise moving %-formatting and {}-formatting into the same page that is not stdtypes.  4.7.2 is a pretty long section, and it seems odd to me that it is still in that page instead of with the other string formatting specs, though it is the only place that would have made sense in a pre-{}-and-$-formatting world.

On the other hand, Gerrit's proposed solution is a *lot* simpler :)
History
Date User Action Args
2014-01-20 17:34:44zach.waresetrecipients: + zach.ware, barry, georg.brandl, docs@python, Gerrit.Holl
2014-01-20 17:34:44zach.waresetmessageid: <1390239284.35.0.828903006004.issue20314@psf.upfronthosting.co.za>
2014-01-20 17:34:44zach.warelinkissue20314 messages
2014-01-20 17:34:44zach.warecreate