[feat]If t-string can have a template method to combine the string

[DannyWuzhiheng]

Feature or enhancement

Proposal:

I think it would be even better if t-string had a method (like s=template.combine()) to return the combined result.
（maybe had been mentioned by someone, or already implemented.）

Actually，It's not a method to change the template into a string but return a string like the f-string , I dont't know if there is a method or a fuction to implementation this，but I can only use the join() method of string to do this now

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

[picnixz]

cc @davepeck

I think such additional feature needs to be discussed first on DPO as well.

[davepeck]

Yeah, there are a whole bunch of follow-on/utility methods we could (and probably should) consider adding. I should probably read over past DPO threads and put together a suggested list of potential additions for further discussion...

[picnixz]

Thanks. I will close this issue as not planned for now so that you can gather the various threads & issues together and ask on DPO which interfaces should be implemented. I don't like having an issue where it's not clear if (and when) we need this feature.

Before closing this, @DannyWuzhiheng could you actually show an example of some combine() method and how it would behave. I don't understand quite well what you mean by the "combined" result. It's possible to concatante t-strings together (but not t-strings and simple str).

[DannyWuzhiheng]

I mean just doing things like to return the string after combining
like this piece of code

name = "DannyWuzhiheng"
template=t"Hello {name}"
s=template.combine()
print(s)

and output
Hello DannyWuzhiheng

also It maybe better if there are some arguments,but I haven't think about that
If there's anything more,please call me on the email
new email danny_wuzhiheng@qq.com

[picnixz]

So you mean something to evaluate the template, like a format(). Didn't we want to avoid this explicitly when drafting the PEP? (just closing it as "not planned" for now)

[davepeck]

Didn't we wanted to avoid this explicitly when drafting the PEP?

Yes. Specifically, we intentionally avoided implementing a custom Template.__str__ because the key feature of templates is that you must explicitly decide how you want to process them: how to handle the interpolations, and how to do so safety.

@DannyWuzhiheng Out of curiosity, why would you like to do this? Would f-strings be a better choice for your use case?

(PS: If you'd like an example implementation of what you're calling combine(), see the f() function in the pep750-examples repository.)