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 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 > > in sympy, because many users just have python2.4 as default, i.e. > > Debian has switched to python2.5 just couple days (!) ago. All people > > running gentoo, or Debian stable, or Debian testing have python2.4. > > People can blame Debian for being slow, but I don't care, those are > > the real life constrains, and I rather view it as a fact, that python > > import statements were insufficient for a long time, so it also takes > > a long time to get this fixed for all users. > > > > > > > > You could add something to your setup.py that deletes > the old site-package/sympy/* files, before doing the > standard things it does (calls the setup function). Then > Sympy's setup would work fine with any Python install. > Give it a shot.
I added exactly this into the spkg-install script: http://trac.sagemath.org/sage_trac/ticket/2941 Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
