On 06 septembre 12:06, Dan Stromberg wrote: > On Mon, Sep 6, 2010 at 2:09 AM, Sylvain Thénault < > sylvain.thena...@logilab.fr> wrote: > > > On 01 septembre 11:35, Emile Anclin wrote: > > > On Monday 16 August 2010 14:08:25 Tshepang Lekhonkhobe wrote: > > > > On Thu, Aug 12, 2010 at 23:03, Tshepang Lekhonkhobe < > > tshep...@gmail.com> > > > wrote: > > > > > I'll try to propose a plan corresponding to what is explained on python > > > doc: > > > > > > 1) make logilab-common run on py3k (i.e. make the tests work). > > > this should also make pytest run on python3.X > > > I believe we need that to run the tests on astng and pylint; > > > > no, as I said I don't want to bother with pytest/testlib in the py3k port > > since those both module are a dead end. And they represent 25% of lgc's > > code... > > I presume you have some other means of invoking the tests in mind? Perhaps > the new unittest2-based code?
with python >= 2.7: alias pytest='python -m unittest discover' with python < 2.7: alias pytest='unit2 discover' unit2 being provided by unittest2. -- 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
