[issue17078] string.Template.safe_substitute hard-wires "braces" as {}

Changes by Georg Brandl : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue17078] string.Template.safe_substitute hard-wires "braces" as {}

Georg Brandl added the comment: Done in 8a98ee6baa1e. Thanks! -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list maili

[issue17078] string.Template.safe_substitute hard-wires "braces" as {}

Sam Kimbrel added the comment: Florent Xicluna already fixed this in r84888 for 3.2+; I've tested that the patch applies cleanly to 2.7 and tests pass. Someone with the commit bit should transplant that commit into 2.7 as it does not change the public API to this module. -- nosy: +sam

[issue17078] string.Template.safe_substitute hard-wires "braces" as {}

Éric Araujo added the comment: Barry, I read that passage in the PEP to explain why the default style uses ${}, but the bug here is about a Template class with an overriden placeholder pattern. -- nosy: +eric.araujo ___ Python tracker

[issue17078] string.Template.safe_substitute hard-wires "braces" as {}

Barry A. Warsaw added the comment: See PEP 292 and the section titled "Why `$' and Braces?" http://www.python.org/dev/peps/pep-0292/ -- ___ Python tracker ___ __

[issue17078] string.Template.safe_substitute hard-wires "braces" as {}

Changes by R. David Murray : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue17078] string.Template.safe_substitute hard-wires "braces" as {}

New submission from Adam Kellas: If you use safe_substitute and try to use a variable reference style other than ${foo}, you will find that it assumes ${foo} style. In particular, when evaluating $[foo] (square braces) and 'foo' is not defined, safe_substitute will put the string back together