[SciPy-Dev] PR 397: Getting rid of 2to3 (single codebase for Python 2 & 3)
Sat Jan 5 14:54:17 CST 2013
On Sat, Jan 5, 2013 at 2:15 PM, Pauli Virtanen <email@example.com> wrote:
> Prompted by this:
> here's a conversion of the Scipy code base runnable on Python 2.6 and
> 3.x without 2to3:
> That was fairly easy to do, and I suspect the case is the same for Numpy.
> But do we want to go this way? On the one hand, this is a cleaner way to
> go than relying on 2to3 --- which does not convert all semantic
> differences and can lead to some subtle bugs...
> On the other hand, well, you have to add list() around map() et al. to
> make them lists, and have to import xrange, izip et al. from a
> compatibility module.
> To me, overall, this doesn't look like a bad route to go. Thoughts?
I looked through your changes in scipy stats. They don't look too
difficult and I don't see a reason not to switch to this.
Some things might be difficult to remember and might slip through pull requests.
For example for statsmodels I need to do compatibility fixes (with
python and older numpy) at irregular intervals, which got easier
however with having python 3 tested by TravisCI.
> SciPy-Dev mailing list
More information about the SciPy-Dev