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 docs@python, eli.bendersky, eric.araujo, ezio.melotti
Date 2011-07-27.17:08:31
SpamBayes Score 0.00010959823
Marked as misclassified No
Message-id <1311786512.26.0.0868134897043.issue12644@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, the note should probably be clarified to mention that if precision is specified, only the first precision characters will be shown. The field width is covered globally (for all conversion types) in note 4 above the table.

While we're at it, note 5 is:

   Precision (optional), given as a '.' (dot) followed by the precision. If specified as '*' (an asterisk), the actual width is read from the next element of the tuple in values, and the value to convert comes after the precision.

I think that the second sentence should have "the actual precision" instead "the actual width".
History
Date User Action Args
2011-07-27 17:08:32eli.benderskysetrecipients: + eli.bendersky, ezio.melotti, eric.araujo, docs@python
2011-07-27 17:08:32eli.benderskysetmessageid: <1311786512.26.0.0868134897043.issue12644@psf.upfronthosting.co.za>
2011-07-27 17:08:31eli.benderskylinkissue12644 messages
2011-07-27 17:08:31eli.benderskycreate