You may want to have a look at the deferred PEP 501 -- General purpose string interpolation: https://www.python.org/dev/peps/pep-0501/ It was proposed while PEP 498 -- Literal String Interpolation (f-string) was being discussed, which was accepted: https://www.python.org/dev/peps/pep-0498/ PEP 501 proposed a solution for i18n. Victor Le mer. 4 déc. 2019 à 10:22, Anders Munch <ajm@flonidan.dk> a écrit :

Chris Angelico [mailto:rosuav@gmail.com] wrote:

...

The first one is already the case. PEP 414 reintroduced the u"..." literal form, specifically as a porting tool. Given that it has absolutely zero value in pure Py3 code [...]

Challenge accepted :) Here comes my https://xkcd.com/1172/ moment.

I'm using the u prefix to tag user interface strings for translation. u"..." goes through i18n, "..." doesn't. I have tools that extract and replace texts, identify new strings for translation etc. based on this. I was very happy when 3.3 reintroduced the prefix, because it allowed me to upgrade without losing my very efficient workflow. Not to mention having to make 10.000 code changes to replace the prefix with something or other.

If the prefix goes, I'm not going to complain, I know my setup is fairly unique and I can't really demand that you keep vestigial syntax around just for that. But I'd still be sorry to see it go.

regards, Anders _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/WCZDU2M2... Code of Conduct: http://python.org/psf/codeofconduct/

-- Night gathers, and now my watch begins. It shall not end until my death.