Beginning with Release 4.1.2, "sage -sh" was adjusted and now completely strips the users environment as set in the various .*rc files.
I'm assuming there were collisions between variables needed by sage and those the user may be setting. However, this recent change seems extreme and makes using the sage shell problematic (and somewhat annoying). I didn't see discussion or rationale for the change although I'm sure there were good reasons. Without understanding exactly what the reason was, however, makes it hard to know how to fix its side effects without breaking whatever was being fixed. Of note: in bash, "PS1" was changed and now prints an extra line with the $SAGE_ROOT value in addition to "sage subshell$". Thats a whole lotta warning and, IMHO, overdone. This is easily fixed but brings up another issue... is it now necessary to have a .sagerc and some strategy for combining .bashrc and .sagerc so users can maintain consistency? I've previously reported what I consider inconsistencies in how sage sets environment variables (#6610). I'm guessing that something broke so a "clean room" approach to environment variables was taken. I would prefer that we identify what needs to be set and be a bit more surgical WRT the sage environment, at least for the sage shell. -glenn -- Glenn H. Tarbox, PhD || 206-274-6919 || [email protected] - xmpp || ghtdak - aim,jabber,IRC,yahoo --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
