pyxl3

PEP 750 started its life in part as a result of learnings from pyxl [0], which used some clever hacks to add a JSX-like syntax to Python. In the end, my instinct is that t-strings are the better more generic feature to add to the language itself today. That said, I'd love to see the Python ecosystem get to the point where it's relatively easy to implement transpilers and get new grammars integrated with key tools (colorizers, formatters, linters, type checkers, etc). After that: let a thousand JSX-likes bloom. [0] https://github.com/gvanrossum/pyxl3

The idea is you can register a custom file encoding, analogous to built-in file encodings like utf-8, and use it to transform the source file before python loads it. An example is pyxl, kind of like jsx, where you put `# coding: pyxl` at the top and then it will transform bare `<html>` in the python file into calls to a template builder: https://github.com/gvanrossum/pyxl3 Incidentally this turns out to be super hard to search for without asking an LLM, since "python coding" is so overloaded, and using the feature this way is intentionally undocumented because it's not really what it's for, and not something I think most python users really want to encourage. So, forbidden python knowledge!

Check this project: https://github.com/gvanrossum/pyxl3

yes https://github.com/gvanrossum/pyxl3

Indeed it is. Guido himself maintained a project called Pyxl3 [1] for a while (forked from one at Dropbox during his tenure there) that abused this codec feature to implement something similar to JSX within Python source. [1] https://github.com/gvanrossum/pyxl3

Also similar in name to "Pyxl", like React JSX for Python https://github.com/gvanrossum/pyxl3