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 ? 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 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) -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
