On Wed, 3 Sep 2014 20:50:53 +0100
Stuart Henderson wrote:
> On 2014/09/03 21:43, frantisek holop wrote:
> > Stuart Henderson, 03 Sep 2014 20:34:
> > > > so basically:
> > > >
> > > > 1. one single py2 version
> > > > 2. py3 flavor, installed with bin/pyflakes${MODPY_VERSION}
> > > > 3. py3 flavor
On 2014/09/03 21:43, frantisek holop wrote:
> Stuart Henderson, 03 Sep 2014 20:34:
> > > so basically:
> > >
> > > 1. one single py2 version
> > > 2. py3 flavor, installed with bin/pyflakes${MODPY_VERSION}
> > > 3. py3 flavor, conflict marker
> > >
> > > i am inclined to go with (1) until py2 is
Stuart Henderson, 03 Sep 2014 20:34:
> > so basically:
> >
> > 1. one single py2 version
> > 2. py3 flavor, installed with bin/pyflakes${MODPY_VERSION}
> > 3. py3 flavor, conflict marker
> >
> > i am inclined to go with (1) until py2 is widespread.
> > i see (2) as waste of space. (3) is a bit
>
On 2014/09/03 21:18, frantisek holop wrote:
> this question is more specifically about pyflakes
> update i am working on.
>
> it has one codebase that works both for py2 and py3
> files. so in theory it needs no flavor, just
> have a py2 version and use that for py3 as well.
> at the moment this
On Wed, Sep 03, 2014 at 09:18:39PM +0200, frantisek holop wrote:
> this question is more specifically about pyflakes
> update i am working on.
>
> it has one codebase that works both for py2 and py3
> files. so in theory it needs no flavor, just
> have a py2 version and use that for py3 as well.
this question is more specifically about pyflakes
update i am working on.
it has one codebase that works both for py2 and py3
files. so in theory it needs no flavor, just
have a py2 version and use that for py3 as well.
at the moment this is likely not an issue, because
most people will probably
