Message151592
| Author |
skrah |
| Recipients |
Retro, eric.smith, py.user, skrah |
| Date |
2012年01月19日.00:34:54 |
| SpamBayes Score |
4.3261858e-05 |
| Marked as misclassified |
No |
| Message-id |
<20120119003453.GB23755@sleipnir.bytereef.org> |
| In-reply-to |
<1326930156.77.0.87659655019.issue13811@psf.upfronthosting.co.za> |
| Content |
Eric V. Smith <report@bugs.python.org> wrote:
> As I look at it a little closer, I think I'm going to change the message to:
> "Invalid format type specified". The code has determined that instead of a
> type that's a single character long, it's received "xx10d". That's because
> "xx" doesn't match any of "[[fill]align][sign][#][0][width][,][.precision]",
> so it must be the "[type]" field.
I think this has the potential of being more confusing for people who are
not very familiar with the format specification mini-language. I didn't
look at the code now, but would the message also be raised for this spec?
format(9, "xx10f")
> I'm open to a better message, though.
IMO "invalid format specifier" is fine. Even the existing error message
is not really terrible. |
|