Eric Smith e...@trueblade.com added the comment:
The root of this problem is an interaction with ',' formatting that was
introduced in 2.7 and 3.1. I'm still trying to figure out how to implement it.
I'm changing the priority to low because I can't imagine this is a problem in
practice. If
Changes by Jeong-Min Lee false...@gmail.com:
--
nosy: +falsetru
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6902
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6902
___
Nick Coghlan ncogh...@gmail.com added the comment:
Note that the 2.6 branch didn't seem to suffer this problem when I
checked it earlier tonight.
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6902
Eric Smith e...@trueblade.com added the comment:
complex will also need to be addressed. The second error message is
misleading, for the same reason the formatting on float and int is
incorrect:
format(3-2j, 030)
Traceback (most recent call last):
File stdin, line 1, in module
ValueError:
New submission from Eric Smith e...@trueblade.com:
Originally discussed in issue 6871. Even if an alignment of is
specified, = is used if the padding character is 0.
format(2, '020')
'0002'
format(2, '120')
'2111'
This is a problem for at least float and
