Georg S Weber found a problem with the Mac app [1] which is caused by running sage via an applescript via sage-native-execute after having sourced sage-env. What happens is the variable SAGE_ENV_SOURCED is set to 1 and then the applescript runs opening an Terminal window and calling sage. So when sage is run it sees that SAGE_ENV_SOURCED is 1 and doesn't try to set the environment variables, but in the meantime PATH has become "messed up" leaving the system python to be found first. But even if PATH was set correctly, LD_LIBRARY_PATH would not.
To make a long story short anytime sage is executed from sage-native-execute bad things might happen. I'm wondering if we can just unset SAGE_ENV_SOURCED in sage-native-execute or if that will cause some problems that I don't forsee because sage-env gets sourced twice. I already have a patch up at #12161 working around it in the Mac app, but I think it might be cleaner to make the change to sage-native-execute. -Ivan [1] http://trac.sagemath.org/sage_trac/ticket/12161 -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
