headers
jbi130 | 3 Mar 2004 23:00
Picon
Favicon

License and redistribution.

I'm looking at using Twisted for a commercial application, this may
involve distribution pyPgSQL with our application.  While the license
looks very BSD like, there is the clause "without fee".

Is the intention here to now allow distribution of pyPgSQL with
commercial (read, $$)?

There are no issues with Twisted as its LGPL.

Thanks.

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
Permalink | Reply | 2 comments |
headers
Billy G. Allie | 4 Mar 2004 05:45
Picon

Re: License and redistribution.


jbi130@... wrote:
| I'm looking at using Twisted for a commercial application, this may
| involve distribution pyPgSQL with our application.  While the license
| looks very BSD like, there is the clause "without fee".
|
| Is the intention here to now allow distribution of pyPgSQL with
| commercial (read, $$)?
|
No, it just means that you can distribute it without paying a fee to do so.

--
____       | Billy G. Allie    | Domain....: Bill.Allie@...
|  /|      | 7436 Hartwell     | MSN.......: B_G_Allie@...
|-/-|----- | Dearborn, MI 48126|
|/  |LLIE  | (313) 582-1540    |
Permalink | Reply | 0 comments |
headers
Mike C. Fletcher | 4 Mar 2004 06:07
Favicon

Re: License and redistribution.

What you are seeing there is the "CWI Python License" or the "CWI 
permissions statement and disclaimer", which is the basis on which the 
CNRI and later the PSF Python licences were built.  If you can use 
Python in your app, you can use a piece of software licensed under that 
license, (if only considering the licenses).

HTH,
Mike

Obviously, I'm not a lawyer :) .

jbi130@... wrote:

>I'm looking at using Twisted for a commercial application, this may
>involve distribution pyPgSQL with our application.  While the license
>looks very BSD like, there is the clause "without fee".
>
>Is the intention here to now allow distribution of pyPgSQL with
>commercial (read, $$)?
>
>There are no issues with Twisted as its LGPL.
>
>Thanks.
>  
>
_______________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://members.rogers.com/mcfletch/
(Continue reading)

Permalink | Reply | 0 comments |
headers
charlie clark | 25 Mar 2004 15:54

Problems with the Zope PyPgSQL adaptor

Dear list,

I've been looking for a Python driver for PostgreSQL support and it seems 
that PyPgSQL is currently the only one to offer this. The driver seems to 
work fine so I tried the ZopeDA from CVS. This seems to have several 
problems: first of all I was not able to set up a connection using 
standard parameters:
e.g dbname=charlie host=localhost as the connection string
I get an error complaining that the database "dbname=charlie" doesn't 
exist. So I've hard-coded the connection string in db.py. It might be nice 
to know what I'm doing wrong.

The other error is that with or without unicode supports, result sets seem 
to have some kind of memory problem. Testing a single SELECT causing my 
system to run out of memory with Python swelling to well over 150 MB 
(probably more if I had the resources) and pg_ctl crashing at some point 
being unable to allocate heap to the child. I thought this might be 
related to unicode but it isn't.

System: Zope 2.6.2 (binary release, python 2.1, win32-x86), python 2.1.3, 
win32), PostgreSQL 7.4.1 for cygwin.

Any ideas?

Charlie

--

-- 
Charlie Clark
Helmholtzstr. 20
Düsseldorf
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Blüm | 30 Mar 2004 21:19
Picon
Picon

getting fetching messages...

hello,

I almost pulled out all my hair over this.

I have a simple INSERT INTO for a couple of values. there is a trigger that
skips the insertion and spits out an INFO line telling me that this record is
already in the table (_if_ it already is, otherwise the trigger returns the
to-be-inserted-row and stays quiet)

I just want python to get these INFO-lines right after the query:
'INFO:  record already in table: text7112343o'

this doesn't work:
...
dbcon.query("BEGIN")
for bla in dataarray:
  insertstring="INSERT INTO testtable VALUES ('"+bla+"')"
  dbcon.query(insertstring)
  print "### ", dbcon.notifies()
dbcon.query("COMMIT")
...

Traceback (most recent call last):
  File "import1.py", line 22, in ?
    print "### ", dbcon.notifies()
AttributeError: notifies

...why...?

any help's greatly appreciated.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Blüm | 31 Mar 2004 11:04
Picon
Picon

Re: getting fetching messages...

On Wed, 31 Mar 2004 08:38:31 +0200
gerhard quell <gquell@...> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Do you mean:
> 
> ~ dbcon.notices() ?
> 
> Gerhard
> - ------------
> Alexander Blüm wrote:
> | hello,
> |
> | I almost pulled out all my hair over this.
> |
> | I have a simple INSERT INTO for a couple of values. there is a
> trigger that
> | skips the insertion and spits out an INFO line telling me that this
> record is
> | already in the table (_if_ it already is, otherwise the trigger
> returns the
> | to-be-inserted-row and stays quiet)
> |
> | I just want python to get these INFO-lines right after the query:
> | 'INFO:  record already in table: text7112343o'
> |
> | this doesn't work:
> | ...
(Continue reading)

Permalink | Reply | 1 comment |
headers
gerhard quell | 31 Mar 2004 15:23
Picon

Re: getting fetching messages...


Hi Alexander,

~  sorry, you're using the pygresql-Modul, not our pyPgSQL-Modul!

The needed function is getnotify(), which returns a message from your
server! Look in the manuals!

Gerhard
-------------

Alexander Blüm wrote:
| On Wed, 31 Mar 2004 08:38:31 +0200
| gerhard quell <gquell@...> wrote:
|
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Do you mean:
|>
|>~ dbcon.notices() ?
|>
|>Gerhard
|>- ------------
|>Alexander Blüm wrote:
|>| hello,
|>|
|>| I almost pulled out all my hair over this.
|>|
(Continue reading)

Permalink | Reply | 0 comments |

Gmane