Actually universal newline support seems to be covered by the following PEP
and is present in the version of Python(2.3) I am running.
http://www.python.org/peps/pep-0278.txt
I would tend to agree with Hong Yuan that the problem exists in plpythonu's
handling of newlines.
On Tuesday 18 January 2005 05:19 am, Tom Lane wrote:
> Michael Fuhr <mike@fuhr.org> writes:
> > 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."
>
> Seems like Guido has missed a bet here: namely the case of a script
> generated on one platform and fed to an interpreter running on another.
> If I were designing it, I would say that any Python interpreter should
> take all three variants no matter which platform the interpreter itself
> is sitting on. Or is cross-platform support not a Python goal?
>
> In short, any bug report on this ought to go to the Python project.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
--
Adrian Klaver
aklaver@comcast.net
