On Monday, December 30, 2013 12:35:37 PM UTC-8, R. Andrew Ohana wrote: > Moreover, I don't think we have to force the switch, it should be > perfectly possible to support both python 2 and python 3 for a period of > time. >
What's the benefit of that? The sage process itself will be running on one python process. We can't be hybrid with that. So either you make the whole sage library Py3-capable or not. We could ship both Py2 and Py3 so that we can run some scripts under Py3 and the sage process under Py2 (or vice versa), but having two pythons seems a lot of admin for very little benefit. I could see a development version that for a while has both to aid debugging adapting the sage library, but outside of that I don't see a benefit of having both. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
