On 06 septembre 11:59, Dan Stromberg wrote: > On Mon, Sep 6, 2010 at 1:59 AM, Sylvain Thénault < > > are you sure you're not testing system installed logilab.common ? > > I was. > > To get around this, I propose: > 1) Make the hierarchy in common's source directory mirror more closely what > goes into site-packages, in particular, making the automatically-created > __init__.py at the top no longer be automatically created. > 2) Introduce top-level 2.x and 3.x directories, where the 2.x directory has > the official sources (for now), and 3.x is automatically derived at > "setup.py install" time from 2.x using sa2to3. I'm not sure to understand the pb you're trying to solve here. > > > When is the new unit testing code to arrive? I'd like to look it over > > soon > > > > it's just a matter of time to 1. switch existing test to unittest2, then to > > 2. > > ensure we can do what we use to do with pytest using discover (and > > eventually > > contribute missing feature). Regarding py3k port, #1 is enough so that we > > can > > just igore lgc.testlib and lgc.pytest modules. > > It seems likely that if the unittest2 code isn't merged first, substantial > merge conflicts will result.
There is no merge to do, simply stop using logilab.common(lgc).testlib in tests. > That is, assuming that we get pytest working on 3.x. I'm not sure I > understand why that wouldn't be desireable? Simply because we don't intend to maintain it now that unittest2 and discover are becoming standard. So why bothering converting it to py3k... -- 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 Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
