Groups > comp.lang.python > #197464

Re: backslash in triple quoted string

From	Greg Ewing <greg.ewing@canterbury.ac.nz>
Newsgroups	comp.lang.python
Subject	Re: backslash in triple quoted string
Date	2025-05-13 12:11 +1200
Message-ID	<m8fh11F2ufiU1@mid.individual.net> (permalink)
References	(6 earlier) <CAJQBtgkPegbJJbuseHGGgN5qjUYvctYGo6T4oO+ysJg2jJ71Sg@mail.gmail.com> <mailman.41.1746976932.3008.python-list@python.org> <m8d4u1FlrmkU1@mid.individual.net> <CAJQBtgk-9Hn0xVq3CHnGnJ9CDvc_5+qz5gPZnW2z5zHFc+=WKA@mail.gmail.com> <mailman.49.1747074494.3008.python-list@python.org>

Show all headers | View raw

On 13/05/25 6:28 am, Left Right wrote:
> Read the associate release note.

I take it you're referring to this:

> In a future Python version, SyntaxError will
> eventually be raised, instead of SyntaxWarning. (Contributed by Victor
> Stinner in gh-98401.)

That doesn't contradict what I said. Currently it's a warning. If and 
when it becomes an error, presumably the grammar documentation will be 
updated to reflect that. If it isn't, you'll have cause to complain, but 
not before.

-- 
Greg

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar

Thread

Re: backslash in triple quoted string Left Right <olegsivokon@gmail.com> - 2025-05-11 17:21 +0200
  Re: backslash in triple quoted string Greg Ewing <greg.ewing@canterbury.ac.nz> - 2025-05-12 14:32 +1200
    Re: backslash in triple quoted string Left Right <olegsivokon@gmail.com> - 2025-05-12 20:28 +0200
      Re: backslash in triple quoted string Greg Ewing <greg.ewing@canterbury.ac.nz> - 2025-05-13 12:11 +1200

csiph-web