On Jan 21, 2:15 pm, Ivan Andrus <darthand...@gmail.com> wrote: > 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.
There are other things that sage-native-execute messes up. For instance, any python invocation almost certainly leads to mayhem, because PATH/PYTHONPATH/LD_LIBRARY_PATH are inconsistent. See http://trac.sagemath.org/sage_trac/ticket/9386 -- 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
