> I have moved the development of sympy/sandbox to a new project > sympycore: > > http://code.google.com/p/sympycore/ > > as there is lots of work ahead to improve the assumptions model among > other > things and much faster core in sympycore is already usable for many > applications. > > The plan is to keep copying code from sympy project minimal so that it > would be easier > to keep track on the new improved features in sympycore and not to mix > old coding techniques with new ones.
Indeed the SymPy's motivation is to have something usable now and it's true that I am more concerned with functionality rather than with speed. But I would like to have just one symbolic library in Python, not two with slightly different ways of doing things. Of course if there were problems with deciding how to implement things, it would make sense to have two projects, each doing it differently - but I don't think that's the case. I only require each thing to be discussed first. So it would be good if we could reuse most of the work you do, but that means someone needs to implement it back in SymPy. If that happens, it's fine. If we manage to disentagle the core from the rest of SymPy, that'd be of course awesome. But as I said earlier, I am quite skeptical on this -- and I don't want it to end up in a way that sympycore will have some very nice features and speed that SymPy doesn't and SymPy will have some very nice functionality that sympycore doesn't and it will be impossible to merge it, so that one could either use one or the other. That could happen easily, because we may realize we don't have time to merge all the sympycore with SymPy as well as you may realize you don't have time to merge all SymPy with sympycore. That way we would fail to build a car and just endup with two incompatible components. That's why I want to integrate SymPy closely with SAGE, so that people can use just one tool. But it makes sense to have SymPy as a separate project, because it's pure Python and small and I like the philosophy of having one small tool doing one job and doing it well. If we could make SymPy depend on the sympycore, it also make sense to have it as a separate, well defined project (that could possibly be rewritten in C++/C), doing one job and doing it well. Sorry for a longer email, I just wanted to make sure we try to avoid some common pitfalls. 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 -~----------~----~----~----~------~----~------~--~---
