| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hong Yuan <hongyuan(at)homemaster(dot)cn>, aklaver(at)comcast(dot)net, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Multiline plpython procedure |
| Date: | 2005-01-18 07:49:11 |
| Message-ID: | 20050118074911.GA17229@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 18, 2005 at 01:24:31AM -0500, Tom Lane wrote:
>
> It seems odd that in today's climate the Python interpreter
> would not cope well with Windows-style newlines. Maybe there is some
> configuration issue with Python itself?
http://docs.python.org/ref/physical.html
"A physical line ends in whatever the current platform's convention
is for terminating lines. On Unix, this is the ASCII LF (linefeed)
character. On Windows, it is the ASCII sequence CR LF (return
followed by linefeed). On Macintosh, it is the ASCII CR (return)
character."
And yet simple tests show that normal scripts run on Unix-like
platforms regardless of whether their lines end in LF, CRLF, or CR.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mstory | 2005-01-18 07:57:43 | Re: Users and unique identifyers |
| Previous Message | Michael Fuhr | 2005-01-18 07:39:08 | Re: Multiline plpython procedure |