On Thu, Sep 3, 2009 at 7:16 PM, jjh<j...@42quarks.com> wrote: > > > > On Sep 4, 12:12 pm, jjh <j...@42quarks.com> wrote: >> What is the best way to fix this (and submit a patch). Is it just that >> once a version of Sage is compiled for 10.6 the libraries will no >> longer conflict and the problem will go away? Or should I change >> matlab.py to call sage-native-execute before matlab? Or should I >> change expect.py or pexect.py to always shed the DYLD_LIBRARY_PATH >> environment variables? Or something else? > > It looks like Octave has a similar issue. Should the change be made in > Expect to run all external commands with sage-native-wrapper or will > that break other things? > http://trac.sagemath.org/sage_trac/ticket/5858
That will definitely break things. But you should definitely run all *external* commands to packages external to sage through sage-native-execute. In particular, change MATLAB to do that and please submit a patch. Thanks!! William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
