issue with string.Template

[Michele Simionato]

This is somewhat in between a bug report and a feature request.
I was using the new string.Template class and I have run into a
few issues that I traced back to the usage of the idiom

'%s' % val

in the 'convert' helper function in Template.substitute.

I do not understand why '%s' % val was used instead of just
str(val).

'%s' % val in unfortunate since it results in the following
surprising (for me) behavior:
'hello'

[not '("hello",)']
TypeError: not enough arguments for format string

[not '()']

Is this intended behavior? It is surprising since it is
different from what one would expect from old-fashioned string
interpolation
'()'

which is the behaviour I find most useful. Also, I do not like
that different expressions such as
T("$obj").substitute(obj=("hello",))
and T("$obj").substitute(obj="hello") give the same output
(this potentially hides type bugs).

So, take this as a bug report if the behavior is not intended and
as a feature request if the current behaviour is the intended
one

Michele Simionato

P.S. at the end, the problem is that string interpolation with
positional arguments is somewhat of a hack, but fixing this will
have to wait until Python 3000 ...

 

[Peter Otten]

TypeError: not enough arguments for format string

So, take this as a bug report if the behavior is not intended and
as a feature request if the current behaviour is the intended
one

I vote for bug report. The need to habitually wrap any tuple arguments into
another 1-tuple is clearly at odds with the goal to simplify string
interpolation.

Peter

 

[Raymond Hettinger]

This is somewhat in between a bug report and a feature request.
I was using the new string.Template class and I have run into a
few issues that I traced back to the usage of the idiom

'%s' % val

in the 'convert' helper function in Template.substitute.

I do not understand why '%s' % val was used instead of just
str(val).

The reason is written in the code comments:

"""
# We use this idiom instead of str() because the latter will
# fail if val is a Unicode containing non-ASCII characters.
"""

P.S. at the end, the problem is that string interpolation with
positional arguments is somewhat of a hack, but fixing this will
have to wait until Python 3000 ...

The plan for Py3.0 is to have a formatting function that doesn't have
the same tuple vs scalar issue.

So, take this as a bug report if the behavior is not intended and
as a feature request if the current behaviour is the intended
one

Feel free to post a SF report. If Barry wants to alter the behavior,
it is easy enough to do:

try:
return str(s)
except UnicodeEncodeError:
return unicode(s)


Raymond Hettinger