On Mon, 15 Jan 2007, Fabio Tranchitella wrote:
At this point, everything is more clear to me: you are running a zope 2.8
instance which uses python2.3 but both python-psycopg and python-psycopg2
do not support python2.3 anymore.
Sounds like a very reasonable explanation.
The reason for this choice is related to
the python policy (we'll support only python2.3 in etch) and obviously
I guess you meant: s/2.3/2.4/
there is no zope2.8 package in etch at the moment so the problem is
triggered by your old zope package.
Well, even if I wanted to stik to this verison this is my personal
problem. If we do not support 2.8 than I have to cope with this.
Could you please confirm me the diagnosis? :)
Perfect.
I think the only reasonable thing to do is to drop support for zope2.7 and
zope2.8 from zope-psycopgda and zope-psycopgda2. In this way, it won't be
possible to install them in zope2.[78] instances (which is the right thing
according to the etch python policy).
Yes. This would fix the bug. This would definitely notify people who
want to stick to older versions to grab for backports (or even snapshot.net).
Kind regard and thanks for your quick response
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
