On 2016-08-19 13:11, C Anthony Risinger wrote:
It might be harder to find the end of an f-string in one shot, but I
think that's the crux of the issue: to a reader/developer, is an
f-string conceptually one thing or a compound thing?
To me (someone who would like to see f-string expressions appear like
normal expressions, without extra quoting, and proper syntax
highlighting *always*, just like shell), this argument is essentially
the same as trying to use a regex to find a closing bracket or brace or
parse HTML. It's only hard (disregarding any underlying impl details)
because that view regards f-strings as singular things with only one
"end", when in reality an f-string is much much more like a compound
expression that just happens to look like a string.
Personally I think that is a dangerous road to go down. It seems it
would lead to the practice of doing all sorts of complicated things
inside f-strings, which seems like a bad idea to me. In principle you
could write your entire program in an f-string, but that doesn't mean we
need to accommodate the sort of syntax highlighting that would
facilitate that.
To me it seems more prudent to just say that f-strings are (as the name
implies) strings, and leave it at that. If I ever get to the point
where what I'm doing in the f-string is so complicated that I really
need syntax highlighting for it to look good, I'd take that as a sign
that I should move some of that code out of the f-string into ordinary
expressions.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
