Please consider PEP 750 -- Template Strings
https://peps.python.org/pep-0750/
SIG-specific:
A few related expressions of support for this PEP:
Alyssa Coughlin: "The proposal in PEP 750 covers the use cases that PEP 501 set out to cover. Where there are differences in the scope and technical details, they are well justified in PEP 750’s favour (hence the withdrawal of PEP 501 during the PEP 750 discussions).”
Phil Jones: "I’d like to express my support as I would like to use template strings to build SQL queries and I’ve recently written SQL-tString in anticipation.”
Nicholas Tollervey: “The capabilities PEP 750 brings would be wonderful for PyScript, and I want to make sure Damien has a heads up so MicroPython and Pyodide have some sort of parity.” (Note: a core PyScript implementer has been working with us on a template language.)
The authors also had meetings with Barry Warsaw (flufl.i18n), David Lord (Jinja), and Andreas Pelme (htpy).
Thanks again for your time & consideration! :-)
Please consider PEP 750 -- Template Strings
https://peps.python.org/pep-0750/
Post-HistoryheaderPost-History)SIG-specific:
A few related expressions of support for this PEP:
Alyssa Coughlin: "The proposal in PEP 750 covers the use cases that PEP 501 set out to cover. Where there are differences in the scope and technical details, they are well justified in PEP 750’s favour (hence the withdrawal of PEP 501 during the PEP 750 discussions).”
Phil Jones: "I’d like to express my support as I would like to use template strings to build SQL queries and I’ve recently written SQL-tString in anticipation.”
Nicholas Tollervey: “The capabilities PEP 750 brings would be wonderful for PyScript, and I want to make sure Damien has a heads up so MicroPython and Pyodide have some sort of parity.” (Note: a core PyScript implementer has been working with us on a template language.)
The authors also had meetings with Barry Warsaw (flufl.i18n), David Lord (Jinja), and Andreas Pelme (htpy).
Thanks again for your time & consideration! :-)