Many thanks for the help. William's suggestion that it is better using an independently-installed gnuplot did the trick - adding gnuplotpy via sage -i gnuplotpy-1.7.p3 once gnuplot was up and running from the command line worked.
If anyone wants to investigate why sage -i gnuplot-4.0.0 didn't work I'd be happy to send more of the log file (but please tell me how you'd like this to be done!). However as this package is experimental I can see this would be low priority. Patrick. On Feb 8, 8:37 am, William Stein <[email protected]> wrote: > On Sun, Feb 8, 2009 at 12:21 AM, mabshoff > > > > <[email protected]> wrote: > > > On Feb 8, 12:13 am, William Stein <[email protected]> wrote: > > > <SNIP> > > >> I hope the following is helpful. > > >> The only reason for an end user to install the gnuplot package is of > >> they can't install it any other way. Sage doesn't do any binary > >> linking at all to gnuplot. As long as a gnuplot command is installed > >> and in their path, things should work. The user does have some > >> gnuplot installed, evidently, but it's probably not setup to run by > >> typing "gnuplot" in Terminal. They probably need to make a script > >> called "gnuplot" in their PATH and put something like this in it: > > >> -------------- > >> #!/bin/sh > >> path/to/gnuplot $@ > >> ------------- > > > Before Nick Alexander has an aneurysm :) - this should be > > > -------- > > #!/bin/sh > > path/to/gnuplot "$@" > > -------- > > Oh crap. Somebody should open a trac ticket to fix my brain!! And > make it a blocker. > > William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
