is psycopg2 broken in etch?
[if this is better suited for another list please let me know] Hi list! I have (very simple) python program that makes use of psycopg2 to access a postgresql database (still very simple). Pretty much by a "lucky accident" I realized that something is seriously broken -- running the same program with the same data does NOT produce the same data in the database. Given the overall simplicity -- one process/thread, one connection to DB with commit() after each insert, I don't think anything in the program can explain the behavior. Googling on the subject I found this comment in Ubuntus bugs system: James Henstridge wrote on 2007-09-05: (permalink) Note that the 2.0.5 release of psycopg2 has other serious problems, such as not reporting errors from commit(). So if an update is going to be made available for previous versions of Ubuntu, it would be better to backport the latest version rather than trying to backport just the 64-bit fix. Since I'm on Debian/Etch amd64, I wonder if the "natural" version of psycopg2 (2.0.5.1-6) have had any fixes backported from never versions? On a side note I tried to bring back the version from Sid (using apt-get source ...) but there were too many dependencys for me to feel comfort about. Is there some easy way to "strip it" from stuff I know I wont be using (e.i. debug and zope packages)? Sincerely yours, Emil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is psycopg2 broken in etch?
Hello Emil, * 2008-07-17 17:18, Emil Pedersen wrote: > I have (very simple) python program that makes use of psycopg2 to access > a postgresql database (still very simple). Can you post here your script? It would help to debug the situation. > Since I'm on Debian/Etch amd64, I wonder if the "natural" version of > psycopg2 (2.0.5.1-6) have had any fixes backported from never versions? I think 2.0.5.1 already contains the fix (2.0.5.1 != 2.0.5). > On a side note I tried to bring back the version from Sid (using apt-get > source ...) but there were too many dependencys for me to feel comfort > about. Is there some easy way to "strip it" from stuff I know I wont be > using (e.i. debug and zope packages)? You have to rebuild the package in etch, because it contains a binary library which is depending on a newer libc6 and so on. Best regards, -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is psycopg2 broken in etch?
--On torsdag, juli 17, 2008 17.22.07 +0200 Fabio Tranchitella <[EMAIL PROTECTED]> wrote: Hello Emil, Hello Fabio! Sorry for the delay, thanks for getting back to me! * 2008-07-17 17:18, Emil Pedersen wrote: I have (very simple) python program that makes use of psycopg2 to access a postgresql database (still very simple). Can you post here your script? It would help to debug the situation. I removed most of the unused stuff but it's still about 150 lines so I've included a link to it (the full of it), and also the table definition. If it is ok to post such a long script to the list I'll happily do it. http://83.253.255.25/tmp/ Since I'm on Debian/Etch amd64, I wonder if the "natural" version of psycopg2 (2.0.5.1-6) have had any fixes backported from never versions? I think 2.0.5.1 already contains the fix (2.0.5.1 != 2.0.5). Could be, I tried to find something about it in some changelog but didn't find much (neither that it was fixed nor that it was not). Btw I forgot the url to the forementioned note: https://bugs.launchpad.net/ubuntu/+source/psycopg2/+bug/108067 and here is the one for psycopg2: http://www.initd.org/pub/software/psycopg/ChangeLog-2.0 On a side note I tried to bring back the version from Sid (using apt-get source ...) but there were too many dependencys for me to feel comfort about. Is there some easy way to "strip it" from stuff I know I wont be using (e.i. debug and zope packages)? You have to rebuild the package in etch, because it contains a binary library which is depending on a newer libc6 and so on. Oush, sounds nasty. // Emil Best regards, -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
