Re: Multiline plpython procedure

From: Stuart Bishop <stuart(at)stuartbishop(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org
Subject: Re: Multiline plpython procedure
Date: 2005-01-21 07:28:22
Message-ID: 41F0AF16.2080503@stuartbishop.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Greg Stark <gsstark(at)mit(dot)edu> writes:
>
>>Egads. So the set of valid Python programs is different depending on what
>>platform you're on? That's just, uhm, insane.
>
>
> No quibble here.
>
>
>>Incidentally, are we sure we've diagnosed this correctly? I'm discussing this
>>with some Python developers and they're expressing skepticism. One just tried
>>a quick test with a Python program containing a mixture of all three newline
>>flavours and it ran fine.
>
>
> He tried reading 'em from files, using Python's text-format-converting
> file reader, no? See the test case posted up-thread, which demonstrates
> that feeding a string directly to PyExec (or whatever its called)
> produces newline-sensitive results.

This is currently being discussed on python-dev:

http://mail.python.org/pipermail/python-dev/2005-January/051203.html

It looks like my earlier concerns were unwarrented - current consensus
seems to be to transform line endings in the string to the
one-true-format expected by Python's guts:

http://mail.python.org/pipermail/python-dev/2005-January/051214.html

--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stuart Bishop 2005-01-21 07:39:06 Re: Best Linux Distribution
Previous Message Dann Corbit 2005-01-21 06:57:27 Re: Calculating a moving average