[Python-Dev] Should PEP 498 specify if rf'...' is valid?
Ryan Gonzalez
rymg19 at gmail.com
Wed Oct 21 22:57:17 EDT 2015
More information about the Python-Dev mailing list
Wed Oct 21 22:57:17 EDT 2015
- Previous message (by thread): [Python-Dev] PEP 484 -- proposal to allow @overload in non-stub files
- Next message (by thread): [Python-Dev] Should PEP 498 specify if rf'...' is valid?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It mentions fr'...' as a formatted raw string but doesn't say anything about rf'...'. Right now, in implementing PEP 498 support in Howl (https://github.com/howl-editor/howl/pull/118 and https://github.com/howl-editor/howl/commit/1e577da89efc1c1de780634b531f64346cf586d6#diff-851d9b84896270cc7e3bbea3014007a5R86), I assumed both were valid. Should the PEP be more specific? BTW, at the rate language-python is going, GitHub will get syntax highlighting for f-strings in 2050. :D -- Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20151021/3fc2c886/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 484 -- proposal to allow @overload in non-stub files
- Next message (by thread): [Python-Dev] Should PEP 498 specify if rf'...' is valid?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list