On 14 septembre 14:29, Emile Anclin wrote:
> Hello,
Yo,
> Trying to port logilab-common to py3k, I fixed all '-3' warnings, and
> tested to import from unittest2 instead of unittest; and then I run 2to3.
>
> Here is what I found:
>
> 2/ unittest2 vs. unittest:
> there are actually (at least)
Hello,
Trying to port logilab-common to py3k, I fixed all '-3' warnings, and
tested to import from unittest2 instead of unittest; and then I run 2to3.
Here is what I found:
1/ Warnings and 2to3:
I built some patches / quick fixes to disable the
python2.6 -3 warnings. Unfortunately the "-3"
On Thu, Sep 09, 2010 at 02:47:06PM +0200, Julien Jehannet wrote:
> Just a note to remind that some of our assertions methods in lgc.testlib
> don't have equivalent implementations in unittest2/py2.7-unittest (yet).
>
> Maybe in a first step, depending of the unittest version, we could start
> by a
On 09 septembre 19:19, Emile Anclin wrote:
> I meant that we need the time to fix the "-3" Warnings, like the quick
> fixes as attachement. I just had a fast look, and could not find how
> migrating os.path.walk to os.walk. Does anybody know ?
>
> We can ignore all compat warnings I guess. So th
On Thursday 09 September 2010 11:37:57 Sylvain Thénault wrote:
> On 09 septembre 11:24, Emile Anclin wrote:
> > I might be missing something, but as far as I can see, if we only
> > care about pylint-3k, it seems to me easier to translate
> > pytest to py3k than to make all tests run with unit2:
>
> * Sylvain Thénault [09-sep-2010 11:38]:
>
> The point is that time is hard to find, and we'll *have* to kill
> pytest/testlib
> since we don't want to use them indefinitly while we've viable alternative
> in the std lib. So I'ld prefer to go directly that way instead of spending
> half a day t
On 09 septembre 11:24, Emile Anclin wrote:
> I might be missing something, but as far as I can see, if we only care
> about pylint-3k, it seems to me easier to translate
> pytest to py3k than to make all tests run with unit2:
>
> As I have been told, pytest works with importing unittest2 (hence
On Wednesday 08 September 2010 08:31:18 Sylvain Thénault wrote:
> > > 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?
>
> Unfortunatly not. logilab.com
On 07 septembre 18:41, Dan Stromberg wrote:
> On Mon, Sep 6, 2010 at 10:59 PM, Sylvain Thénault <
> > On 06 septembre 11:59, Dan Stromberg wrote:
> > > On Mon, Sep 6, 2010 at 1:59 AM, Sylvain Thénault <
> > > 1) Make the hierarchy in common's source directory mirror more closely
> > what
> > > goes
On Mon, Sep 6, 2010 at 10:59 PM, Sylvain Thénault <
sylvain.thena...@logilab.fr> 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
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, Tshepan
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
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
On Wed, Sep 1, 2010 at 2:35 AM, Emile Anclin wrote:
>
> I had some thoughts on the py3k port:
>
> * as I understand it, pylint for python 2.X will only run against 2.X
> and pylint3 will have to run against 3.X: the reason is that the _ast
> module used for astng will parse the code as 2.X / 3.X, a
On Mon, Sep 6, 2010 at 1:59 AM, Sylvain Thénault <
sylvain.thena...@logilab.fr> wrote:
> On 28 août 18:42, Dan Stromberg wrote:
> > Aside from skipped mxDateTime issues, I've got only unit test error now:
> >
> > ERROR: test_ustrftime_before_1900 (unittest_date.DateTC)
> >
On 06 septembre 14:35, Emile Anclin wrote:
> > > 3) pylint; make tests pass with py3k, write new visit_* methods and
> > > test...
> >
> > there should be no need for new visit_* methods, beside if we want
> > new functionnalities.
>
> Well, the minimal Pylint-3k program could indeed consist of ju
On Monday 06 September 2010 11:09:08 Sylvain Thénault wrote:
> > c) deal with 'print' as a function and the other modifications
>
> I don't think we need anything special to deal with print as a
> function. It will simply be treated as other functions.
right, we have no visit_print method in py
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
> wrote:
> > > Hi,
> > >
> > > So where do I start if I want Pylint ported to Py3k? Is there a
> > > branch somewhere?
> >
> > Thanks
On 28 août 18:53, Dan Stromberg wrote:
> BTW, I think SqlAlchemy's sa2to3 wrapper for 2to3 is probably the best way
> to go for creating code that runs on 2.x and 3.x. This way, you have 2.x
> and 3.x in the same file, distinguished by comments - things are the same on
> both by default, or you ad
On 28 août 18:42, Dan Stromberg wrote:
> Aside from skipped mxDateTime issues, I've got only unit test error now:
>
> ERROR: test_ustrftime_before_1900 (unittest_date.DateTC)
> --
> Traceback (most recent call last)
> File
> "/u
On Monday 16 August 2010 14:08:25 Tshepang Lekhonkhobe wrote:
> On Thu, Aug 12, 2010 at 23:03, Tshepang Lekhonkhobe
wrote:
> > Hi,
> >
> > So where do I start if I want Pylint ported to Py3k? Is there a
> > branch somewhere?
>
> Thanks for the great responses. It's a little confusing though, so c
On Sunday 29 August 2010 03:42:29 Dan Stromberg wrote:
> If I run:
>
> /usr/local/cpython-2.5/bin/python2.5 /usr/local/bin/pytest
>
> ...I get lots of useful output.
>
> If I run:
>
> /usr/local/cpython-2.5/bin/python2.5 ./pytest.py
>
> ...I get no output whatsoever.
/usr/local/bin/pytest is
BTW, I think SqlAlchemy's sa2to3 wrapper for 2to3 is probably the best way
to go for creating code that runs on 2.x and 3.x. This way, you have 2.x
and 3.x in the same file, distinguished by comments - things are the same on
both by default, or you add magic comments that say "Do it this way for 2
On Mon, Aug 23, 2010 at 12:13 AM, Sylvain Thénault <
sylvain.thena...@logilab.fr> wrote:
> On 20 août 16:24, Dan Stromberg wrote:
> > 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
> > m
On Sunday 22 August 2010 23:20:48 Nicolas Chauvat wrote:
> On Wed, Aug 18, 2010 at 08:01:12AM +0200, Sylvain Thénault wrote:
> > 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 do not have a problem with
On Fri, Aug 20, 2010 at 04:24:30PM -0700, Dan Stromberg's pytest wrote:
> Ran 388 test cases in 11.22s (0.20s CPU), 15 errors, 5 failures, 21 skipped
> 17 modules OK (6 failed)
> failures:
> /home/dstromberg/src/pylint-3k/common/build/lib/logilab/common/test/unittest_configuration
> [1/13],
> /home
On 20 août 16:24, Dan Stromberg wrote:
> 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.
duh? You should have a common/test/data directory, I get it properly on clone.
> Do we req
On 22 août 23:20, Nicolas Chauvat wrote:
> On Wed, Aug 18, 2010 at 08:01:12AM +0200, Sylvain Thénault wrote:
> > 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 do not have a problem with http://wiki.pyt
On Sun, Aug 22, 2010 at 2:20 PM, Nicolas Chauvat wrote:
> On Wed, Aug 18, 2010 at 08:01:12AM +0200, Sylvain Thénault wrote:
> > 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 do not have a problem with
On Wed, Aug 18, 2010 at 08:01:12AM +0200, Sylvain Thénault wrote:
> 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 do not have a problem with http://wiki.python.org/moin/PyLint-3k,
but do not understand why h
On Fri, Aug 20, 2010 at 2:21 PM, Tshepang Lekhonkhobe wrote:
> On Fri, Aug 20, 2010 at 21:42, Dan Stromberg wrote:
> >
> > On Tue, Aug 17, 2010 at 11:01 PM, Sylvain Thénault
> > wrote:
> >>
> >> On 17 août 18:47, Dan Stromberg wrote:
> >> > On Mon, Aug 16, 2010 at 5:08 AM, Tshepang Lekhonkhobe
>
On Fri, Aug 20, 2010 at 21:42, Dan Stromberg wrote:
>
> On Tue, Aug 17, 2010 at 11:01 PM, Sylvain Thénault
> wrote:
>>
>> On 17 août 18:47, Dan Stromberg wrote:
>> > On Mon, Aug 16, 2010 at 5:08 AM, Tshepang Lekhonkhobe
>> > wrote:
>> > > Thanks for the great responses. It's a little confusing th
On Tue, Aug 17, 2010 at 11:01 PM, Sylvain Thénault <
sylvain.thena...@logilab.fr> wrote:
> On 17 août 18:47, Dan Stromberg wrote:
> > On Mon, Aug 16, 2010 at 5:08 AM, Tshepang Lekhonkhobe <
> tshep...@gmail.com>wrote:
> > > Thanks for the great responses. It's a little confusing though, so can
> >
On 17 août 18:47, Dan Stromberg wrote:
> On Mon, Aug 16, 2010 at 5:08 AM, Tshepang Lekhonkhobe
> 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
On Mon, Aug 16, 2010 at 5:08 AM, Tshepang Lekhonkhobe wrote:
> On Thu, Aug 12, 2010 at 23:03, Tshepang Lekhonkhobe
> wrote:
> > Hi,
> >
> > So where do I start if I want Pylint ported to Py3k? Is there a branch
> > somewhere?
>
> Thanks for the great responses. It's a little confusing though, so
On Mon, Aug 16, 2010 at 11:02:00AM +0200, Sylvain Thénault wrote:
> On 14 août 13:07, Dan Stromberg wrote:
> As a code checker, pylint is expected to run on as many version as possible.
> We only recently dropped 2.2 support. IMO, dropping support for python <= 2.4
> is fine (and allow a big cleanu
On Thu, Aug 12, 2010 at 23:03, Tshepang Lekhonkhobe wrote:
> Hi,
>
> So where do I start if I want Pylint ported to Py3k? Is there a branch
> somewhere?
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
On 15 août 16:36, Nicolas Chauvat wrote:
> I suppose Sylvain was talking about the branch
> http://hg.logilab.org/logilab/common/graph/318b3b3a166a that was
> committed 17 months ago, but maybe there is something more recent than
> that lying around somewhere. The thing is that many things were
> c
On 14 août 18:31, Dan Stromberg wrote:
> Another question: logilab-common seems to be larger than pylint itself.
> Does pylint use all of logilab-common? logilab-common seems to hold a
> bunch of miscellaneous code.
Indeed, but as Nicolas said, pylint heavily uses it. Though most of the
code is
On 14 août 13:07, Dan Stromberg wrote:
> > > For starters, you could probably look over the various changes in 3.0 and
> > > 3.1, and compile a list of what needs to change in the code.
> > >
> > http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=list+of+changes+in+python+3
> > >
> > > >From t
Hi again,
On Sat, Aug 14, 2010 at 06:31:48PM -0700, Dan Stromberg wrote:
> Another question: logilab-common seems to be larger than pylint itself.
> Does pylint use all of logilab-common? logilab-common seems to hold a
> bunch of miscellaneous code.
pylint$ rgrep -h 'from logilab.common' * | g
On Sat, Aug 14, 2010 at 01:13:43PM -0700, Dan Stromberg wrote:
> > I've checked out the sources with:
> > hg clone http://www.logilab.org/hg/pylint
> > hg clone http://www.logilab.org/src/logilab/astng
> > hg clone http://www.logilab.org/src/logilab/common
> >
>
> BTW, do all three of these have a
Hi Dan,
On Sat, Aug 14, 2010 at 01:07:07PM -0700, Dan Stromberg wrote:
> What do the owners of the code think about attempting to come up with a
> version that runs on (though not _necessarily_ against) 2.6, 2.7 and 3.x
> unmodified? This would almost certainly mean this new version would not run
Another question: logilab-common seems to be larger than pylint itself.
Does pylint use all of logilab-common? logilab-common seems to hold a
bunch of miscellaneous code.
--
Dan Stromberg
___
Python-Projects mailing list
Python-Projects@lists.logilab.
On Sat, Aug 14, 2010 at 1:07 PM, Dan Stromberg wrote:
>
> I've checked out the sources with:
> hg clone http://www.logilab.org/hg/pylint
> hg clone http://www.logilab.org/src/logilab/astng
> hg clone http://www.logilab.org/src/logilab/common
>
BTW, do all three of these have automated test suite
On Thu, Aug 12, 2010 at 10:58 PM, Sylvain Thénault <
sylvain.thena...@logilab.fr> wrote:
> On 12 août 16:02, Dan Stromberg wrote:
> > On Thu, Aug 12, 2010 at 2:08 PM, Shashwat Anand <
> anand.shash...@gmail.com>wrote:
> > > On Fri, Aug 13, 2010 at 2:33 AM, Tshepang Lekhonkhobe <
> tshep...@gmail.c
On 12 août 16:02, Dan Stromberg wrote:
> On Thu, Aug 12, 2010 at 2:08 PM, Shashwat Anand
> wrote:
>
> >
> >
> > On Fri, Aug 13, 2010 at 2:33 AM, Tshepang Lekhonkhobe
> > wrote:
> >
> >> Hi,
> >>
> >> So where do I start if I want Pylint ported to Py3k? Is there a branch
> >> somewhere?
> >>
> >>
On 13 août 03:49, Maarten ter Huurne wrote:
> On Friday 13 August 2010, Dan Stromberg wrote:
>
> > There's also the issue of whether pylint would run on python 2 while
> > checking python 3, or run on python 3 while checking python 3 - I don't
> > know if there's some AST library that would need t
On Friday 13 August 2010, Dan Stromberg wrote:
> There's also the issue of whether pylint would run on python 2 while
> checking python 3, or run on python 3 while checking python 3 - I don't
> know if there's some AST library that would need to match or not.
If astng cannot find the Python sourc
On Thu, Aug 12, 2010 at 2:08 PM, Shashwat Anand wrote:
>
>
> On Fri, Aug 13, 2010 at 2:33 AM, Tshepang Lekhonkhobe
> wrote:
>
>> Hi,
>>
>> So where do I start if I want Pylint ported to Py3k? Is there a branch
>> somewhere?
>>
>>
> I have no idea. But please do so. It is _needed_.
>
I agree that
On Fri, Aug 13, 2010 at 2:33 AM, Tshepang Lekhonkhobe wrote:
> Hi,
>
> So where do I start if I want Pylint ported to Py3k? Is there a branch
> somewhere?
>
>
I have no idea. But please do so. It is _needed_.
> --
> blog: http://tshepang.tumblr.com
>
Hi,
So where do I start if I want Pylint ported to Py3k? Is there a branch
somewhere?
--
blog: http://tshepang.tumblr.com
___
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects
52 matches
Mail list logo
