I am not convinced of tying `backticks` for a single markup language. Different markup languages presumably have different escape methods? Is Python supposed to be explicitly an HTML based language like many of the design choices of JavaScript?

It also seems like a lot to ask to introduce yet another way of quoting strings which doesn't fit with the existing pattern of string quoting. Python already has single quotes, double quotes, triple single quotes, triple double quotes, and all of these can have an r or f placed in front of them to modify their behavior.

I see you have a section on not using the "i" prefix, but I don't understand the sentence "This is an handy feature, which would not work reliably if there are two different prefixes". What is it trying to say? What would not work reliably and why?

I would like to see this PEP have a section on handling security, this PEP implies the Python standard library will safely escape HTML for you which presumably has security implications? And a section on how it will be updated when/if the HTML specification gets updated that may introduce new ways HTML can/must be escaped. And a section on what are the valid versions of HTML it supports? HTML5 only or does it explicitly support older versions of HTML?

Damian (he/him)

On Fri, Sep 3, 2021 at 9:47 AM Thomas Güttler <info@thomas-guettler.de> wrote:
Some weeks ago I started the idea of Template Literals for Python:


I just switched to a new company (descript.de) and diving into their context
will need some time.

This means I won't work on the Template Literals PEP.

If you like the idea, then it would be great if you work on it.

Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-leave@python.org
Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/BZWBK2PFBFUXU5PEP7UZORHL23RQVHE4/
Code of Conduct: http://python.org/psf/codeofconduct/