Hi Pearu,
> 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
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
> 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 pl
On Oct 16, 8:29 am, "Fredrik Johansson" <[EMAIL PROTECTED]>
wrote:
>
> Seems like a viable approach. Could you add me as a developer?
Sure. Done.
Pearu
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sympy" gro
On 10/16/07, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> 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 sympyco
Hi,
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
