On Tue, Jul 7, 2009 at 1:27 PM, Aaron S. Meurer<[email protected]> wrote: > > Will these changes have to go in a separate sympy-py3k release or will > they be backwards compatible with Python 2? I think that we should > put whatever is backwards compatible in the main release. I know a > lot of it is cleaning up imports, which will be good for both > versions. For example, I cannot currently import all() from within > mul.py because __init__.py in utilities has a "from sympy import *" > line in it that doesn't play so nice at that level. Issue 1454 is > also related to this.
Yes, I plan to put as many fixes into our main branch. To release python3 version would ideally amount to: 1) download our main branch 2) run the 2to3 tool 3) ./setup.py sdist And in fact ./setup.py can get some parameter to run the 2to3 tool automatically. This is the ideal, in practise the 2to3 tool needs improvements upstream to handle sympy well. The other changes should be possible to backport. In any case, I will do my best not to maintain two branches of sympy. The same as with cython, I'll do my best not to maintain a cython branch and a sympy branch. Currently unfortunately cython also needs improvements upstream. Ondrej --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
