The new dependency caching code breaks when SAGE_ROOT is a symlink. Easy fix: don't have SAGE_ROOT be a symlink. But symlink's are convenient...
The issue is in module_path, which doesn't recognize that SAGE_ROOT and the absolute path of its input could not be text identical. It could be fixed to be more robust. It seems simpler -- and might prevent later problems -- if ~/sage/ sage checked if SAGE_ROOT is a valid symlink and if so, converted it to an absolute path. Any thoughts ? I'm not thrilled twiddling a user's setting so early in the game... Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
