On Mon, Sep 6, 2010 at 10:59 PM, Sylvain Thénault < [email protected]> wrote:
> 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. Actually, there are two problems I'm hoping to solve with this. One is to have a directory that contains an exact mirror of what will go into site-packages, to facilitate testing. That way, you can set PYTHONPATH and your tests are comparing apples to apples. The other is... To me it seems the best way of getting 3.x sources from 2.x is with sa2to3. But I believe sa2to3 is going to want to have two distinct files for each module, one for 2.x, and one for 3.x. The clearest way of distinguishing between these is to have two distinct but closely related hierarchies: One authoritative (2.x), and the other 100% automatically generated from the other (3.x). Please note that eventually the relationship could conceivably be reversed with 3to2. > > > 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. You are saying that the difference is solely in how the tests are invoked from the command line? -- Dan Stromberg
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
