Closed cyrus- closed 6 years ago
If this is a problem with the upstream code that astunparse is based on, I'd be happy to file the bug elsewhere -- just let me know where it should go.
Seems like it should be fixed in #19
Just checked it out, doesn't seem to fix the problem in this issue...
This is (should now be) fixed in v1.6.0. (Please reopen if I missed something.)
In the description of PEP 498, there is an example of a format specifier that itself contains interpolated values:
https://www.python.org/dev/peps/pep-0498/#format-specifiers
The unparse method doesn't seem to handle this well:
Notice that the part after
value:
is not bare but rather inside a format string, which isn't valid. The correct behavior should be: