Petri Lehtinen <pe...@digip.org> added the comment: I've played around with the str.format() code for a few weeks now, to investigate its poor performance compared to the % operator.
Having written a few parsers before, I would change it to parse each part separately: 1. field_name 2a. if followed by '[': element_index (anything until ']') 2b. elif followed by '.': attribute_name 3. if followed by '!': conversion 4. if followed by '}': format_spec (anything until '}') It seems to me that the documentation also suggests this behavior, and that this bug report is correct. What comes to parsing identifiers, it seems to me that stopping at '.', ']', and '}' is not enough. In field_name, '[', ':' and '!' would also be needed, and ':' and '!' in attribute_name. It's a shame that PEP3101 is so vague on this subject. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12014> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
