Revision history [back]

Based on my brief experiments, I think it is a PATH issue. Within a single notebook, you should be able to do

os.environ['PATH'] += ':/opt/local/bin:/Applications/Macaulay2-1.20/bin/'

and then Sage should be able to find the relevant executables. If this works, then you can create a file $HOME/.sage/init.sage containing that command. The commands in init.sage are executed every time you run Sage, so this will automatically modify your PATH every time you run Sage.

Based on my brief experiments, I think it is a PATH issue. Within a single notebook, you should be able to do

os.environ['PATH'] += ':/opt/local/bin:/Applications/Macaulay2-1.20/bin/'

and then Sage should be able to find the relevant executables. If this works, then you can create a file $HOME/.sage/init.sage containing that command. The commands in init.sage are executed every time you run Sage, so this will automatically modify your PATH every time you run Sage.

Based on my brief experiments, I think it is a PATH issue. Within a single notebook, you should be able to do

os.environ['PATH'] += ':/opt/local/bin:/Applications/Macaulay2-1.20/bin/'

and then Sage should be able to find the relevant executables. If this works, then you can create a file $HOME/.sage/init.sage containing that command. The commands in init.sage are executed every time you run Sage, so this will automatically modify your PATH every time you run Sage.

(In a little more detail, I think that the Mac binaries intentionally use a limited value for the PATH variable: they do not just read it from your environment. So you need to modify PATH yourself if you want something beyond the default for the Sage Mac app.)