Message168468
As I read the docs, the error message is correct and this issue is invalid as a behavior issue. I read the OP's second message as more or less saying this also.
"'=' Forces the padding to be placed after the sign (if any) but before the digits. This is used for printing fields in the form ‘+000000120’. This alignment option is only valid for numeric types."
"If the width field is preceded by a zero ('0') character, this enables zero-padding. This is equivalent to an alignment type of '=' and a fill character of '0'."
So ":02" is equivalent to ":0=2", which is invalid.
>>> '{:02d}'.format(1)
'01'
works fine.
I decided make this a doc issue and add " for numeric types" after "this enables zero-padding" before closing this. |
|
Date |
User |
Action |
Args |
2012-08-17 19:13:31 | terry.reedy | set | recipients:
+ terry.reedy, eric.smith, ezio.melotti, docs@python, py.user |
2012-08-17 19:13:31 | terry.reedy | set | messageid: <1345230811.79.0.11932824136.issue15660@psf.upfronthosting.co.za> |
2012-08-17 19:13:31 | terry.reedy | link | issue15660 messages |
2012-08-17 19:13:30 | terry.reedy | create | |
|