On Fri, Aug 20, 2010 at 2:21 PM, Tshepang Lekhonkhobe <[email protected]>wrote:
> On Fri, Aug 20, 2010 at 21:42, Dan Stromberg <[email protected]> wrote: > > > > On Tue, Aug 17, 2010 at 11:01 PM, Sylvain Thénault > > <[email protected]> wrote: > >> > >> On 17 août 18:47, Dan Stromberg wrote: > >> > On Mon, Aug 16, 2010 at 5:08 AM, Tshepang Lekhonkhobe > >> > <[email protected]>wrote: > >> > > Thanks for the great responses. It's a little confusing though, so > can > >> > > you guys create some page (wiki?) somewhere on your site on what > >> > > actually needs to be done by a wannabe like me (with a link tothe > >> > > ticket: http://www.logilab.org/ticket/19645). > >> > > >> > > >> > I like this idea - to describe plans and status on a wiki. Does > logilab > >> > have a wiki? If not, is using the python wiki for a specific > project's > >> > status considered acceptable by the owners of the pylint code and the > >> > maintainers of the python wiki? > >> > >> Until logilab.org grows its own wiki, and that won't occurs until > pylint > >> is ported to py3k (I hope at least ;), it's fine with me. > > > > I've started a Wiki page about the pylint in Python 3 port at: > > http://wiki.python.org/moin/PyLint-3k > > Please feel free, all, to edit with questions, general comments, and > > anticipated technical requirements. > > -- > > Dan Stromberg > > Dan rocks! LOL. :) Where is this "data" directory that pytest complains about in the "common" package? It seems to want a bunch of files in there that I didn't get from mercurial. Do we require the mx.DateTime stuff that pytest is trying to find for common? mx.DateTime doesn't appear to have been ported to 3.x yet. There are things other than the mx.DateTime stuff that is failing in the pytest tests. Is this a known issue? Do any of them need to be fixed before getting further into the 3.x port? Is there a way of running pytest using modules that haven't been setup.py install'd? It'd be nice if my test iterations didn't have to install repeatedly. I was hoping that PYTHONPATH=$(pwd) would help, but it doesn't appear to due to the module hierarchy. I've attached my unit test output from the common package interpreted by a 2.5.x runtime - I tried to include it as text first, but the mailing list shunted my message off to moderation for being too long. -- Dan Stromberg
test-output.bz2
Description: BZip2 compressed data
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
