Sounds like what “module”/lmod are supposed to do automatically for you. Sourcing sage-env effectively give you a sage shell as you would if you run “sage -sh”. Again there is not really a deactivation. It starts a new shell and once you type exit you are out.
But you could try to work out something with that. François > On 17/03/2017, at 17:12, Isuru Fernando <isu...@gmail.com> wrote: > > Hi, > > Conda packages can have a activate.sh and deactivate.sh bash files that are > run when an environment containing that package is activated or deactivated. > > I was thinking about doing "source bin/sage-env" to activate the sage > environment. Problem is that there is no deactivate script that restores the > original environment. Any suggestions? > > > Isuru Fernando > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
