| > Yes, my use case was "I always use F-strings" so these other breakages could not occur, by definition. Unless you're using any dependency at all, including the standard library. > But.. Python has a history of introducing new features that break old ones. It doesn't tho. > That seems to me a balance between backward compatibility and future goodness. That assumes "everything is an fstring" is considered "future goodness", which I'm not sure is a widely shared view. > the "from future import auto-fstring" construct could do it... That seems unlikely as the __future__ pseudo-package has generally been used to opt into hopefully future behaviour. Given the Python 3 experience, somehow, I don't see "let's make all string literals into fstrings" happen any time soon, but hey feel free to create a PEP proposing that. Alternatively, create your own import hook which does this swap before handing the module off of to the compiler. |