> * Sylvain Thénault <sylvain.thena...@logilab.fr> [09-sep-2010 11:38]: > > The point is that time is hard to find, and we'll *have* to kill > pytest/testlib > since we don't want to use them indefinitly while we've viable alternative > in the std lib. So I'ld prefer to go directly that way instead of spending > half a day to do some work that'll be dropped in a near future. > > Also, I don't believe that testlib will actually work with py3k unittest > rewrite, > nor that it's such a big deal to move our tests to unittest2 (hopefuly, though > we won't know that for sure until we give it a try).
Just a note to remind that some of our assertions methods in lgc.testlib don't have equivalent implementations in unittest2/py2.7-unittest (yet). Maybe in a first step, depending of the unittest version, we could start by adding some deprecation messages about renamed methods to ease migration and mask testlib duplicates if detected. -- 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 _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
