On Wed, Apr 16, 2008 at 2:28 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, Apr 16, 2008 at 1:28 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > > However, I even consider this a python fault (i.e. I belive a python
> > > library/module should be working no matter which fi
On Wed, Apr 16, 2008 at 1:28 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> > However, I even consider this a python fault (i.e. I belive a python
> > library/module should be working no matter which files you put
> > around), but I think this could be fixed by using relative imports in
>
> However, I even consider this a python fault (i.e. I belive a python
> library/module should be working no matter which files you put
> around), but I think this could be fixed by using relative imports in
> python2.5.
But then again, we are not going to break compatibility with python2.4
On Tue, Apr 15, 2008 at 6:32 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, Apr 15, 2008 at 9:22 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I have the following problem:
> >
> > 1) current sympy spkg in Sage has a file:
> >
> > /sage/local/lib/python2
On Tue, Apr 15, 2008 at 9:22 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have the following problem:
>
> 1) current sympy spkg in Sage has a file:
>
> /sage/local/lib/python2.5/site-packages/sympy/core/parser.py
>
> that we removed in later versions of sympy, because it has the
