hi, i already posted in python-ideas, but i got no replies, so i’ll post here: in essence i think interpreting escape sequences in f-literals is a *very* bad idea, mainly because i think it’s fundamental that syntax highlighters can highlight code as code. so they should highlight the code parts of f-literals as code to avoid bugs and misunderstandings (parts highlighted as string aren’t expected to execute). for many syntax highlighters, it’s *impossible* to properly highlight python code after this change makes python’s grammar recursive (escaped code in f-literals, doubly-escaped code in escaped f-literals in f-literals, …). i want this changed because i think it’s only done this way to reuse the string tokenization code (i.e. convenience), not for some deeper reason. the RFC even says so. however, f-literals aren’t strings, but expressions, so string tokenization rules shouldn’t apply to the non-string parts. how am i going about changing f-literal grammar before the beta hits? i consider this important enough to defer f-literals to 3.7 if it can’t get in in time. best, philipp Ned Deily <nad@python.org> schrieb am Di., 16. Aug. 2016 um 05:02 Uhr:
On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0a4. 3.6.0a4 is the last of four planned alpha releases of Python 3.6, the next major release of Python. During the alpha phase, Python 3.6 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments.
You can find Python 3.6.0a4 here:
https://www.python.org/downloads/release/python-360a4/
The next planned release of Python 3.6 will be 3.6.0b1, currently scheduled for 2016-09-12. 3.6.0b1 will mark the beginning of the beta phase of Python 3.6; at that time, feature development for 3.6 will be complete and the emphasis will change to fixing bugs and regressions. More information about the release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
--Ned
-- Ned Deily nad@python.org -- []
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/flying-sheep%40web.de