Hi, On Sun, Apr 14, 2013 at 5:03 PM, Aaron Meurer <[email protected]> wrote: > There's also the argument that was raised the last time we talked > about this, which is that Python 2.5 is no longer supported at all by > the core Python, even for security updates. > > By the way, the App Engine supports 2.7 now, so that is less of an > issue (though to be sure, we haven't even been successful in porting > SymPy Live to 2.7: https://github.com/sympy/sympy-live/pull/65). > > I think the fact that the rest of the scientific core stack---numpy, > scipy, IPython, probably most others---no longer support Python 2.5 > means we should probably follow suit. So to me, at this point, the > only question is if any of the 2.5 features are important enough that > we should drop support immediately, or if we should get one more > release out first. I don't think it's worth it to support it beyond > one more release (especially at the rate we release).
Aaron - you've said before I think that you think a common 2 / 3 codebase is not practical at the moment. Do you still think that? Can you say why? It's relevant to this discussion only because a common codebase would benefit so much from Python >= 2.6. Cheers, Matthew -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
