On 14 septembre 14:29, Emile Anclin wrote:
> Hello,

Yo,
 
> Trying to port logilab-common to py3k, I fixed all '-3' warnings, and 
> tested to import from unittest2 instead of unittest; and then I run 2to3.
> 
> Here is what I found:
> 
> 2/ unittest2 vs. unittest:
>  there are actually (at least) four unitest version:
>  unittest from py2.x
>  unittest from py3.1   # more or less port unittest2.7 version to 3k
>  unittest from py3.2   # version with a package and around 10 modules
> 
>  and :
>  unittest2 from py2.x  # backport unittest from 3.2 not yet released 
> 
> pytest works well with unittest2 on py2.x, but not exactly
> with the py3.1-unittest.

let's focus in py 3.2
 
> 3/ testing
>  after fixing some small issues and running 2to3,
>  I had a try running pytest:
> 
> I need to backport the _exc_file method from unittest-2.x,
> 
> and to disable monkeypatching in pytest :
> # unittest._TextTestResult = testlib.SkipAwareTestResult
> # unittest.TextTestRunner = ...
> then I could run the tests that showed me a lot of other issues that 
> should be fixed. But some tests are missing: some modules were just not
> recognized.

Julien spotted this pb iirc. You may work on it with him. That may give
some input to Pierre-Yves which will be in the unittest2/distribute sprint
this weekend.
 
-- 
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

Reply via email to