> * Piotr Dobrogost <[email protected]> [27-juil.-2011 16:50]:
> I tried installing pylint 0.24.0 on Python 3.2.1 (in virtualenv) and got this:
> 
> Although there is a version of unittest2 for Python 3
> (http://pypi.python.org/pypi/unittest2py3k) I think logilab-common (needed by
> pylint) should use std unittest from Python 3 (which unittest2 is a backport 
> of).

Just to be more precise:

We want to use unittest2 for old versions of python2 only. For next
stable versions of python (2.7 and 3.2), the pylint tests should run
against stdlib.

> * Piotr Dobrogost <[email protected]> [28-juil.-2011 09:39]:
> Julien Jehannet <julien.jehannet <at> logilab.fr> writes:
> 
> > Humm, bad smell here how unittest2 backport seems to be compatible with
> > the original inspiration...
> I don't quite get what you mean.

Having unittest2py3k backporting unittest2 gives me the impression
that's a separated project from any version of the stdlib.
We don't want this new dependency in our projects.

> > And of course, we have to stick to the stdlib version with python >= 3.2.
> Why 3.2 and not 2.7?
I spoke about python3 here because unittest module changed a lot between
3.1 and 3.2.
-- 
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

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Python-Projects mailing list
[email protected]
http://lists.logilab.org/mailman/listinfo/python-projects

Reply via email to