On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote: > On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: > >  winbot / zope.app.authentication_py_265_32 > >  winbot / zope.app.http_py_265_32 > >  winbot / zope.app.publication_py_265_32 > >  winbot / zope.app.wsgi_py_265_32 > > zope.testbrowser-caused WebTest version conflict.
I've no idea why these errors disappeared. > I plan to release zope.testbrowser 5.0.0 this week. It should fix these > (and probably cause lots of pain elsewhere, if people use undocumented > internals like .mech_browser directly, which they do). I basically chickened out. IIRC the new webtest-based zope.testbrowser breaks API pretty hard (e.g. you can't use zope.app.testing.functional.FunctionalTestLayer any more; you must create a WSGITestLayer from I-forgot-what-zope.-package). What's worse, it lacks documentation for how you're supposed to migrate from older zope.testbrowser versions (<=4.x) to newer versions (5.x). I will not do a release until this documentation exists. It may take me some time to find the time and remember how everything fits together. It shouldn't be too hard (just find some zope package that did the migration in a py3 branch, then document what it did), but I find my motivation is pretty low this week. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
Description: Digital signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )