Re: plpython function problem workaround

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:17:19
Message-ID: 20050315151719.GA6564@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 15, 2005 at 09:46:54AM -0500, Tom Lane wrote:
> "Sim Zacks" <sim(at)compulab(dot)co(dot)il> writes:
> > I've been looking at the possibility of having a planned CR in the source
> > code and I don't see a case where it would happen.
>
> Does python actually disallow newlines in string literals? That is
>
> x = 'foo
> bar'
>
> Whether you think this is good style is not the question --- is it
> allowed by the language?

You can do

x = """this has
newlines embedded"""

--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Linux transformó mi computadora, de una `máquina para hacer cosas',
en un aparato realmente entretenido, sobre el cual cada día aprendo
algo nuevo" (Jaime Salinas)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Fred Blaise 2005-03-15 15:19:16 Re: pg/plsql question
Previous Message Tom Lane 2005-03-15 15:09:35 Re: Filesystem level backup and 32 / 64 bit