Hi Ondrej, I understand your concerns on the dangers of having two similar projects. However, I think it would be impossible for me to develop the core within the restrictions of the sympy policy for several reasons that I'll discuss below.
The issues that are considered difficult to resolve in the current sympy (such as speed, assumptions model, caching issues) become almost unresolvable within the current sympy development policy (which btw is very good for a mature project). Nobody knows what is the best way to resolve these issues, therefore one must experiment and that may temporarily break lots of code. This is not reasonable with the current state of sympy. This situation of changing-the-core-without-breakage will never get better and so solving the hard issues within sympy policy is quite impossible. I agree that discussing changes is a good thing. We have discussed quite alot what are the fundamental issues in sympy and proposed possible ways of resolving these. As a rule, fixing fundamental issues require fundamental changes. I think it is time to start implementing them and sympycore is a proper place to do it. I have spent lots of effort on sympycore by now (in fact more than I planned initially) and I can say that I see light:) At the moment it is too early to discuss about merging sympycore to sympy but when the time is ready, I think the merge will not be as painful as the first one. Regards, Pearu --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
