On Tue, May 24, 2016 at 1:56 PM, William Stein <wst...@gmail.com> wrote:

> We need a real strategy for migrating users to Python3, and definitely
> not some half-way thing that deals only with the print statement.
>

Just lurking here, but that was precisely the thought that came to my mind.

For reference, what we did in IPython (and I really mean the IPython
kernel, not the notebook/Jupyter/etc) and that has ultimately worked very
well (not that it wasn't a lot of effort in the first place):

- Update the IPython kernel to run from a single source in python 2 or 3.
- Provide users an easy way to install IPython as a python2 or python3
kernel for Jupyter.

This decouples *our* development from the *user's* code.  They can choose,
when they each see fit, whether to run a python2 or a python3 stack. Since
all the major scientific python libraries are py2/3 compatible, the choice
is up to them.

This means that, when they choose to update to py3, they pay the price as
they need to, and they can pay that cost even piecemeal, moving one project
over but not another.

I suspect that flat out mandating a hard sage-py2 to sage-py3 transition at
any given point in time will not work at all, it will cost sage users and
will effectively freeze many of them in the sage-py2 version forever.

Maintaining a py2/3 single-source codebase takes some extra work (and
diligent testing on both platforms) but it's not impossible.  I really
think this is the only viable path for sage if you want to retain your user
base and help them make the transition across the py2/3 divide.

Cheers

f


-- 
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to