On Sat, Feb 21, 2009 at 8:57 AM, John Cremona <[email protected]> wrote: > > > > On Feb 21, 3:45 pm, John Cremona <[email protected]> wrote: >> Thanks for the diagnosis and suggestions. Evidently I did the upgrade >> from a clone, one I made yesterday to review one of those patches.... >> >> Suggestion: since the upgrade already gives a prompt and will not >> continue unless you reply "yes", why not add to that prompt a line >> saying don't go any further unless you are not in a clone. Even >> better, detect whether or not you are in a clone and quite if you are >> (if that is possible). >> >> I'm now doing an upgrade from my rc0 build, not from any clone, and >> we'll see what happens! >> > > The upgrade failed in exactly the same way as above. To recap: I had > a working successful build of sage-3.3.rc0 and was in the main branch > (so starting sage did not give me a message about bing in a different > mercurial branch). I typed "sage -upgrade" followed by "y" at the > prpmpt, and went to work on something else. When I came back it had > finished, so I typed "sage" and got the error already reported: the > banner still says rc0 and there's an error on startup, saying > > ImportError: libpynac-0.1.so.2: cannot open shared object file: No > such file or directory > Error importing ipy_profile_sage - perhaps you should run %upgrade? > WARNING: Loading of ipy_profile_sage failed. > > I particularly like the suggestion that my problem is to upgrade > (which does nothing, of course).
That is an error message from Ipython suggesting to upgrade the Ipython rc files. It's extremely annoying and has nothing to do with the real problem at hand. It's just an instance of Sage not being sufficiently polished, and surely something that would be very confusing to new users. I think we should patch Ipython so it doesn't do that, or at least gives a meaningful error message. -- 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-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
