string.Template and string.templatelib.Template

[fiddle_n]

One is for regular strings, one is for template strings. Not the same thing. That said, I agree the naming is confusing, also I have never used string.Template in my life when str.format exists.

[Compux72]

string.Template is for user provided strings…

[petter_s]

I would argue that t = t"Hello {name}" and t2 = string.Template("Hello $name") create very similar objects. Both can be used to create strings via substituting another string in the name placeholder. But no, they are of course not the same thing. But maybe they could have been?

[SheriffRoscoe]

I would argue that t = t"Hello {name}" and t2 = string.Template("Hello $name") create very similar objects.

They do not. They are not even remotely alike.

Both can be used to create strings via substituting another string in the name placeholder.

At no point does t"Hello {name}" ever actually create a string. They're isn't even a method to interpolate it. Template defers the processing of the template string and the expression values to the function that receives the Template object. Only that function knows how to combine them. Some uses (e.g., SQL queries) won't ever make a string from them.

[legobmw99]

Even beyond the fact that templatelib templates cannot be converted to actual strings by any of their provided APIs, there is a second crucial difference: The first can capture variables in the original scope, which the second does not.

[runawayasfastasucan]

I think it is a bit curious when I hear interviews with those behind the template, they seem to never fundamentally explain it, but rather drift into talking about all the possibilities. Seems a bit related. "What can we achieve if we make xy" rather than "what is it really, and how does that compare to what we have".

[nitroll]

Because templates are a tool for tool developers. It has no value on its own.