Eric Smith e...@trueblade.com added the comment:
Checked in.
trunk: r78440
release26-maint: r78441
py3k: r78442
release31-maint: r78443
--
resolution: - accepted
stage: patch review - committed/rejected
status: open - closed
___
Python tracker
Eric Smith e...@trueblade.com added the comment:
I think the only remaining issue here is that 's' isn't documented. The
exceptions are now more meaningful, and commas have been documented.
--
versions: +Python 3.2 -Python 3.0
___
Python tracker
Eric Smith e...@trueblade.com added the comment:
Here's my proposed changes. Please review.
I put the string type 's' into its own table. That's probably overkill, but I
think it gets lost if it's just mentioned in the text. Feel free to change
that, though.
Also, I'm not wild about my
Eric Smith e...@trueblade.com added the comment:
That looks good. I tweaked it a little and fixed a few other problems with the
patch. New patch attached.
--
Added file: http://bugs.python.org/file16360/issue5965-1.diff
___
Python tracker
Łukasz Rekucki lreku...@gmail.com added the comment:
I see a problem with silently converting types without __format__() using
str(). The user may write `{:10s}.format(some_obj)`, which will work as long
as some_obj doesn't have a formatter of it's own. If I later on, decide I want
to add
Changes by Georg Brandl ge...@python.org:
--
assignee: georg.brandl - eric.smith
nosy: +eric.smith
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5965
___
Eric Smith e...@trueblade.com added the comment:
I'll look at it. The comma stuff needs to be added for 2.7 and 3.1, too.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5965
___
New submission from Terry J. Reedy tjre...@udel.edu:
String Services / Format Specification Mini-Language (7.1.3.1 in 3.1)
Building on #5963: document type 's' and implicit conversions.
Near the top, after
A general convention is that an empty format string () produces the
same result as if you
Terry J. Reedy tjre...@udel.edu added the comment:
I forgot to include:
Error messages for mismatches between specification type and value type
currently look like
ValueError: Unknown conversion type d
They would be *much* clearer written as something like
ValueError: Conversion type d is
