New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[regression] str.format sublevel format parsing broken in Python 3.3.3 #63928
Comments
can't find a way around it... maybe a new regression test on this. Python 3.3.3 (v3.3.3:c3896275c0f6, Nov 18 2013, 21:18:40) [MSC v.1600 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> "0x{:0{:d}X}".format(0x0,16)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: unmatched '{' in format
>>> "0x{:0{{:d}}X}".format(0x0,16)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: Invalid format specifier
>>> "0x{:0{:d}X}".format(0x0,16)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: unmatched '{' in format
>>> "0x{:{:d}X}".format(0x0,16)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: unmatched '{' in format
>>> "0x{:0{:d}X}".format(0x0,16)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: unmatched '{' in format
>>> "0x{:0{:d}x}".format(0x0,16)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: unmatched '{' in format
>>>
>>> "{:0{}x}".format(0,16)
'0000000000000000' "0x{:0{:d}X}".format(0x0,16) and "{:0{}x}".format(0,16) |
Amusingly, it also works in 3.4. |
According to hg bisect, the regression comes from: changeset: 83817:6786e681ed58 |
This broke a lot of our code, I think that priority needs to be raised to urgent. |
my projects are total broken by this, so my temporary solution is to down grade to 3.3.2 somehow we don't have any test to check this before releasing 3.3.3 |
Hmm, sucks. Benjamin, can you come up with a fix? I'll give it a few weeks to wait for more potential regressions and then do a 3.3.4. |
New changeset bab7dc2ffc16 by Benjamin Peterson in branch '3.3': New changeset e27684eed3b6 by Benjamin Peterson in branch 'default': |
Sorry about that. |
just want to know if there is any tentative schedule to release 3.3.4. the PEP for 3.3 schedule doesn't talk about 3.3.4, so I'm not sure if the decision was to leave latest 3.3 with this broken regression or fix it and release 3.3.4. |
New changeset f25d8cbd074a by Martin Panter in branch '3.5': New changeset fe692ee6d19a by Martin Panter in branch '2.7': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: