> * Nicolas Chauvat <[email protected]> [15-déc.-2010 11:34]: > On Wed, Dec 15, 2010 at 11:09:13AM +0100, Julien Jehannet wrote: > > I'm quite sure we don't want advertise too much this "dark corner" of > > logilab.common ;-) The actual trend is to replace testlib and pytest by > > recent changes from unittest/unittest2 (even if not already in stdlib). > > > > So please, conѕider using unittest2 in favor of testlib for your own > > projects. > > If you want to use some "feature" of testlib, please use a copy of the > > module. > > What is the dark corner you mention ? ..heavy patching symptom with a lot of code needed by pytest.py only.
The interesting part was the assertion methods but most of them are now in unittest2. The cleanup is still under way so IMO it's not a good idea to rely on testlib classes (especially SkipAwareTestProgram or SkipAwareTextTestRunner). > The plan for logilab.common.testlib is: > 1/ base it on unittest2 instead of unittest > 2/ remove/refactor everything that duplicates stuff from unittest2 > 3/ if there are things left, try to implement them as plug-ins on top > of unittest2 and offer to include them in the next version Except that the plugin branch in unittest2 is not really functional yet and different from what we have in python2.7 or python3.2. Also, there is no release plan for it at the moment. > 4/ as far as possible, do it transparently so that things that work > with logilab.common.testlib continue working (but maybe printing > out deprecation warnings) So why don't use unittest2 directly ? -- Julien JEHANNET LOGILAB, Paris (France) http://www.cubicweb.org CubicWeb, le cadriciel du web sémantique http://www.logilab.org Dépôt des logiciels libres conçus par Logilab http://www.logilab.fr Informatique scientifique & Gestion de connaissances
signature.asc
Description: Digital signature
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
