zope, zope-popyda, psycopg and python1.5-{,egenix-}mxdatetime

2001-11-19 Thread Joel Rosdahl
Good evening, Does anyone have opinions on this? Is there a need for a python1.5-mxdatetime (based on the old mxdatetime) or a python1.5-egenix-mxdatetime (based on the new egenix mxdatetime)? --- Begin Message --- On Mon, Nov 19, 2001 at 07:33:59PM +0100, Joel Rosdahl wrote: > [EMAIL PROTECTED]

Re: zope, zope-popyda, psycopg and python1.5-{,egenix-}mxdatetime

2001-11-19 Thread Federico Di Gregorio
On Mon, 2001-11-19 at 20:57, Joel Rosdahl wrote: > Good evening, > > Does anyone have opinions on this? Is there a need for a > python1.5-mxdatetime (based on the old mxdatetime) or a > python1.5-egenix-mxdatetime (based on the new egenix mxdatetime)? psycopg currently in incoming has versions w

zope, zope-popyda, psycopg and python1.5-{,egenix-}mxdatetime

2001-11-19 Thread Jim Penny
Thinking about fog's reply: was there an earlier python-egenix-mxdatetime compiled for 1.5? I have Package: python-egenix-mxdatetime Version: 2.0.2-5 Depends: python (>= 2.1), python (<< 2.2), python2.1-egenix-mxdatetime which is certainly not going to be compatible (or even findable) by a zope1

Re: zope, zope-popyda, psycopg and python1.5-{,egenix-}mxdatetime

2001-11-19 Thread Federico Di Gregorio
On Mon, 2001-11-19 at 21:29, Jim Penny wrote: > Thinking about fog's reply: > > was there an earlier python-egenix-mxdatetime compiled for 1.5? > > I have > Package: python-egenix-mxdatetime > Version: 2.0.2-5 > Depends: python (>= 2.1), python (<< 2.2), python2.1-egenix-mxdatetime > > which is

Python2.1 new crashbug (vague report..)

2001-11-19 Thread Martijn Faassen
Hi there, I have strong suspicions something changed with Python2.1 in a recent upgrade in unstable that destabilized it. The symptoms: I maintain a package for Zope called ParsedXML (not in Debian). It comes with an extensive unit test suite to check a DOM interface, the parser, and so on. Less