dev-python/psycopg-2.0.2: psycopg2.extensions.QuotedString().__str__ doesn't return str Reproducible: Always Steps to Reproduce: 1.emerge =dev-python/psycopg-2.0.2 2.python 3.from psycopg2.extensions import QuotedString 4.str(QuotedString("abc")) Actual Results: TypeError: __str__ returned non-string (type str) type(QuotedString("abc")) <type 'psycopg2._psycopg.QuotedString'> Expected Results: "'abc'" type(str(QuotedString("abc"))) <type 'str'> It is fixed in psycopg-2.0.6 and 2.0.7. psyco-2.0.8 has issues with missing symbols as reported in bug #242336 Additionaly psycopg-2.0.2 has a QA issue: * QA Notice: file does not exist: * * dodoc: CREDITS does not exist
Arches: Please stable 2.0.8 to fix this issue. Thanks!
hrm... $ python /usr/share/doc/psycopg-2.0.8/examples/usercast.py Traceback (most recent call last): File "/usr/share/doc/psycopg-2.0.8/examples/usercast.py", line 23, in <module> import psycopg2 File "//usr/lib64/python2.5/site-packages/psycopg2/__init__.py", line 60, in <module> from _psycopg import BINARY, NUMBER, STRING, DATETIME, ROWID ImportError: /usr/lib64/python2.5/site-packages/psycopg2/_psycopg.so: undefined symbol: lo_create
Stable on alpha.
There already is a stabilisation request for >dev-python/psycopg-2.0.2 in bug #242336 and there are also described issues with missing symbols in psycopg-2.0.8. Maybe this bug should depend on that one?
ppc stable
ppc64 stable
I think this bug is superseded by bug #242336
Tightening the postgresql dep isn't possible for the stable version atm.: dev-python/psycopg/psycopg-2.0.8.ebuild: alpha(default/linux/alpha/2008.0/server) ['>=virtual/postgresql-base-8.1'] Same for PPC and PPC64. #268138 filed, once that is done we can resume :)
x86 stable
On my x86 stable machine psycopg-2.0.8 just broke my system, i.e., I got the import error about lo_create.so described in Comment #2. Shouldn't this wait until #268138 is completed for x86?
I think too that psycopg-2.0.8 should not be marked stable for x86 since I have the same problem like in comment 2...
I also have the same problem as #2 on x86 stable If it is any use I found this(although it is old) http://osdir.com/ml/python.db.psycopg.devel/2007-02/msg00031.html
Sorry for the discomfort. I stabled a newer PostgreSQL version.
(In reply to comment #13) > Sorry for the discomfort. I stabled a newer PostgreSQL version. > Thanks for that! I don't know if I'm doing this too soon, but I'm trying to run emerge -atvuND world and here is the result: [ebuild U ] dev-python/psycopg-2.0.8 [2.0.2] USE="-debug -doc% -examples% -mxdatetime%" 243 kB [ebuild U ] dev-db/libpq-8.1.11 [8.0.15] USE="nls pam readline ssl zlib -kerberos -pg-intdatetime -threads" 0 kB [blocks B ] <=dev-db/postgresql-8.1.4 ("<=dev-db/postgresql-8.1.4" is blocking dev-db/libpq-8.1.11) So I think that you should stabilize a newer postgreql version from the 8.1 series, since you've stabilized libpq-8.1.11 .... We're almost there ;-) Thanks again
(In reply to comment #14) > So I think that you should stabilize a newer postgreql version from the 8.1 > series, since you've stabilized libpq-8.1.11 .... Gnah...yes. > We're almost there ;-) Step-by-step. :)
ok, I have emerged the new stable versions of libpq, postgresql and psycopg (dev-db/libpq-8.1.11, dev-db/postgresql-8.1.11, dev-python/psycopg-2.0.8), everything works so far (and the error described in comment 2 is gone)... thanks
dev-python/psycopg-2.0.11 will be stabilized in bug #278366.
