Hello,
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: 1/ Warnings and 2to3: I built some patches / quick fixes to disable the python2.6 -3 warnings. Unfortunately the "-3" option does not see all problems: for instance after the 2to3 transform, 'file' and 'raw_input' were still there and have to be removed. (fileutils.ProtectedFile inherits from file; I don't think it is needed for Pylint, so I skipped it) 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. 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. So, since Pytest does not work well with unittest-3.1, we should probably continue our investigation with python3.2 and hence a more accurate unittest version, or try if we can use the python3.2 version of unittest. (Concerning lgc.table, I know that it is used in 'projman', but it is not needed for pylint) -- Emile Anclin <emile.anc...@logilab.fr> http://www.logilab.fr/ http://www.logilab.org/ Informatique scientifique & et gestion de connaissances _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
