Re: New user: Windows, Postgresql, Python

From: Marco Colombo <marco(at)esi(dot)it>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Paul Moore <pf_moore(at)yahoo(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: New user: Windows, Postgresql, Python
Date: 2005-03-16 12:46:23
Message-ID: 42382A9F.303@esi.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michael Fuhr wrote:
> On Tue, Mar 15, 2005 at 10:46:09PM +0000, Paul Moore wrote:
>
>
>>The long and short of it is that I believe you just use \n to delimit
>>lines on Windows, just like anywhere else.
>
>
> Many thanks -- your test results contain the info we've been seeking.
>

Thanks a lot Paul.

Micheal, you were right.

It seems python documentation is plain wrong, or I'm not able to
read it at all:

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."

This is the language _reference_ manual, btw. I'm very surprised to hear
python on windows is so broken.

Anyway, that makes life simpler for us. plpython programs are \n separated,
no matter what platform the server runs on. Client applications just need
to conply, which is what I suggested some time ago. I'm glad to hear
there's nothing to change on the server side.

.TM.
--
____/ ____/ /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_____/ _____/ _/ Colombo(at)ESI(dot)it

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jason Tesser 2005-03-16 13:07:52 2 questions about types
Previous Message Stanislaw Tristan 2005-03-16 11:41:57 Copression