On 09 septembre 11:24, Emile Anclin wrote: > I might be missing something, but as far as I can see, if we only care > about pylint-3k, it seems to me easier to translate > pytest to py3k than to make all tests run with unit2: > > As I have been told, pytest works with importing unittest2 (hence > Python3k's unittest) instead of unittest.
really? Hard to imagine given monkey patches done by pytest/testlib... > On the other side, I had a quick look at running the tests of lgc with the > python2.6 -3 option : > > $ cd logilab/common > $ python2.6 -3 bin/pytest > > this yields a couple of seemingly simple issues: I would imagine not more > than half a day of work. 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). -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
