| From: | Ragnar Hafstað <gnari(at)simnet(dot)is> |
|---|---|
| To: | David <dbree(at)duo-county(dot)com> |
| Cc: | Sim Zacks <sim(at)compulab(dot)co(dot)il>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: plpython function problem workaround |
| Date: | 2005-03-15 15:41:37 |
| Message-ID: | 1110901297.26975.42.camel@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2005-03-15 at 07:33 -0600, David wrote:
> [about the line-termination problem in plpython]
> I'd like to insert one note here. While I'm not particularly familiar
> with either perl or python, when I encountered the referred-to thread
> regarding Windows/Unix newline incompatibilities in Python, I ran some
> tests on my Linux system. I wrote some very simple scripts in Perl and
> Python and tested them. They ran OK when I saved them in native Linux
> newlines, they ran, but if I saved them in DOS mode (vim), neither the
> Python nor the Perl scripts would run.
actually, perl scripts with \r\n line endings will run just fine in
unix/linux. what you might have been experiencing, is the fact that the
unix shell is expecting \n lineendings, and the #! line could have been
failing to run the perl executable.
gnari
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frederic Massot | 2005-03-15 15:43:01 | Dump all in several files |
| Previous Message | Tom Lane | 2005-03-15 15:34:52 | Re: pg/plsql question |