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 petri.lehtinen
Recipients eric.araujo, ezio.melotti, ncoghlan, petri.lehtinen, terry.reedy
Date 2011-11-18.12:01:46
SpamBayes Score 5.911893e-11
Marked as misclassified No
Message-id <20111118120133.GF3148@p16>
In-reply-to <1321616481.6.0.785282234232.issue13349@psf.upfronthosting.co.za>
Content
Nick Coghlan wrote:
> Please don't stress too much about providing an indication that the
> repr has been truncated - it's an error message, not part of the
> normal program output. Besides, the lack of a closing ')', ']', '}'
> or '>' will usually indicate something is amiss in long reprs.

Ok. This makes things easier.

> More useful would be to raise a separate feature request about the
> lack of width and precision handling for string formatting in
> PyUnicode_FromFormatV - the common format code handling means it
> *accepts* the width and precision information for string codes, but
> then proceeds to completely ignore it. It should be using them to
> pad short strings (width) and truncate long ones (precision), just
> like printf() (only in terms of code points rather than bytes, since
> those codes work with Unicode text).

Created #13428.
History
Date User Action Args
2011-11-18 12:01:47petri.lehtinensetrecipients: + petri.lehtinen, terry.reedy, ncoghlan, ezio.melotti, eric.araujo
2011-11-18 12:01:46petri.lehtinenlinkissue13349 messages
2011-11-18 12:01:46petri.lehtinencreate