Stuart Bishop <stuart@stuartbishop.net> writes:
> Changing this behavior in Python would break backwards compatibility.
Nonsense. It would not affect the behavior of any script that was
accepted before.
> In particular, the exec() function accepts strings that have already been
> unescaped:
> exec('print """\n\r\n\r\n"""')
So? That has nothing to do with the treatment of \r and \n outside a
quoted string.
> I suspect this means fixing this problem in plpythonu for 8.1.
plpython does not have a charter to work around Python bugs. If the
Python community feels that this is correct behavior for Python,
then so be it.
regards, tom lane
