| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
| Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, Adrian Klaver <aklaver(at)comcast(dot)net>, Hong Yuan <hongyuan(at)homemaster(dot)cn>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Multiline plpython procedure |
| Date: | 2005-01-22 05:17:50 |
| Message-ID: | 20366.1106371070@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stuart Bishop <stuart(at)stuartbishop(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-01-22 05:34:51 | Re: plpythonu on 7.4 |
| Previous Message | elein | 2005-01-22 05:16:27 | plpythonu on 7.4 |