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.x,
that way for 3.x".  Then the 2to3 tool is just about guaranteed to be able
to create 3.x code automatically from 2.x, given appropriate annotations.

On Thu, Aug 12, 2010 at 2:03 PM, Tshepang Lekhonkhobe <[email protected]>wrote:

> 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
> [email protected]
> http://lists.logilab.org/mailman/listinfo/python-projects
>



-- 
Dan Stromberg
_______________________________________________
Python-Projects mailing list
[email protected]
http://lists.logilab.org/mailman/listinfo/python-projects

Reply via email to