Vinay Sajip added the comment:
It's not a bug - the reason it's like that is that it allows conversion and
format specifiers to be given - {field_name!conversion:format_spec}.
Of course a more robust solution using regular expressions could be
implemented, but it's not really worth it. If there's a misspelt field name,
generally you'll know because there will either be an exception raised, or (in
production) no output will be produced.
----------
resolution: -> invalid
status: open -> closed
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue17199>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
