Message261861
| Author |
eric.smith |
| Recipients |
docs@python, eric.smith, ezio.melotti, py.user, python-dev, terry.reedy |
| Date |
2016年03月16日.21:03:02 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<56E9CA00.2030302@trueblade.com> |
| In-reply-to |
<1458161762.91.0.990190423499.issue15660@psf.upfronthosting.co.za> |
| Content |
> '''
> When no explicit alignment is given, preceding the width field by a zero ('0') character enables sign-aware zero-padding for numeric types. This is equivalent to a fill character of '0' with an alignment type of '='.
> '''
I think that's good.
> I presume the problem with changing the error message is that it is not immediately known that alignment was set implicitly, by 0 before decimal width, rather than explicitly. If the spec string is still available, it could be searched and the message adjusted if '=' is not present. That proposal should be a new issue if someone wants to push it.
Yes, that's the problem. I guess it would be easier to keep track of
which fields were set via defaults, and which explicitly. Currently,
that information is lost. |
|