Date: Sat, 5 Mar 2005 09:41:44 -0700
From: Michael Fuhr <mike@fuhr.org>
To: Michele Bendazzoli <mickymouse@mickymouse.it>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: plpythonu strange syntax error
Message-ID: <20050305164144.GA70106@winnie.fuhr.org>
References: <1108719498.4676.14.camel@mickymouse.i.mickymouse.it>
	<20050218095623.GA54765@winnie.fuhr.org>
	<1108725960.4676.18.camel@mickymouse.i.mickymouse.it>
	<1108727087.4676.28.camel@mickymouse.i.mickymouse.it>
	<20050218174007.GA66076@winnie.fuhr.org>
	<1110037562.15329.21.camel@mickymouse.i.mickymouse.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1110037562.15329.21.camel@mickymouse.i.mickymouse.it>

On Sat, Mar 05, 2005 at 04:46:02PM +0100, Michele Bendazzoli wrote:

> Yes it works. So the problem is that in Windows system PGAdmin seem to
> create the function with CRLF characters. 
> 
> I don't know if it is a python fault or a pgadmin fault but I think that
> someone should fix it, because it is impossibile to use PGAdmin to
> create plpython function in windows ...

Opinion differs on whose fault it is.  My understanding is that
Python's behavior is intentional, so one could argue that pgAdmin
should take care of the problem.  On the other hand, one could argue
that Python's behavior is silly, and that Python should be fixed.

Since pgAdmin is a more specific tool than Python is, I expect it
would be easier to address the problem in pgAdmin.  But I don't
know enough about pgAdmin to say whether such a "fix" would cause
other problems.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/