Post-Sprint releases done -- a few tests failing
Hi, I just released the last packages after the sprint. While running the compatibility tests of all currently released packages I found the following packages to fail: compat-zope.testing already failed before, the tests seem incompatible with Python 2.4 compat-zope.introspector seems to rely on zapi to be available but not declared as a dependency compat-zope.globalrequest seems to rely on zope.app.testing without declaring the dependency compat-zope.app.keyreference doctest comparison error, probably this is still in flux as Dan is working on that compat-zope.psycopgda compat-zope.sqlalchemy those two fail because of my machine not having compatible libraries around I think in overall we're doing pretty (6 out of 143) well compared to before the sprint (we found quite a few more packages in a broken state) as none of those seem to be "real" problems. Cheers, Christian -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
2009/2/1 Christian Theune <ct@gocept.com>:
compat-zope.app.keyreference doctest comparison error, probably this is still in flux as Dan is working on that
Is that still true? I can't get any error here. Can you provide some detail? Also, you've probably missed a discussion about a bug introduced when refactoring zope.location+zope.traversing: http://mail.zope.org/pipermail/zope-dev/2009-January/034310.html Now to think - there's one more little thing - the getName function for IRoot should return an empty unicode string instead of just self.context.__name__ which is None in case of most root objects:) At least that's what that RootPhysicallyLocatable from zope.traversing does. -- WBR, Dan Korostelev
On Sun, 1 Feb 2009 23:29:41 +0300 Dan Korostelev <nadako@gmail.com> wrote:
2009/2/1 Christian Theune <ct@gocept.com>:
compat-zope.app.keyreference doctest comparison error, probably this is still in flux as Dan is working on that
Is that still true? I can't get any error here. Can you provide some detail?
Also, you've probably missed a discussion about a bug introduced when refactoring zope.location+zope.traversing:
http://mail.zope.org/pipermail/zope-dev/2009-January/034310.html
Now to think - there's one more little thing - the getName function for IRoot should return an empty unicode string instead of just self.context.__name__ which is None in case of most root objects:) At least that's what that RootPhysicallyLocatable from zope.traversing does.
I didn't miss that. I've just not gotten around to that today. It's sunday after all. ;) -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
participants (2)
-
Christian Theune -
Dan Korostelev