On Sat, Sep 10, 2016 at 12:30 PM, Volker Braun <vbraun.n...@gmail.com> wrote: > I think this idea of installing stuff globally (either system-wide or in > ~/.local) is outdated. Really its always better to make a venv if you need > some sort of specialist package. Its just an all-around better workflow. And > Sage-the-distribution really is like a big venv.
I agree with this characterization. Sage-the-distribution is little different from a virtualenv. In fact, perhaps one of the more important steps we could make toward better integration with the system Python is to actually make the Sage environment compatible with virtualenv (e.g. by setting the correct environment variables, and using the site.py from virtualenv, among other things). To me the biggest advantage of that is primarily for developers--I can work on Sage like I work on other Python projects, by running `workon sage` and being plopped into my sage environment. Effectively this would be little different from running "cd path/to/sage/src; ./sage -sh". It's a subtle difference. > I'd rather spend 5 seconds installing my favorite package into Sage than an > hour debugging what in ~/.local makes Sage crash. > > And there are a lot of potential conflicts; for startes if you compile Sage > with SAGE_DEBUG=yes then the Python ABI will be incompatible with any > extension modules in ~/.local > > If anything I would document that you can opt-in to the account-wide > packages by running "PYTHONUSERBASE=~/.local sage" > > > > > > > > > On Friday, September 9, 2016 at 5:38:58 PM UTC+2, William wrote: >> >> Hi, >> >> I personally disagree with trying to make Sage's python and the >> general environment be as isolated as possibly from each other. We >> should try to interoperate with the greater Python world as much as >> possible, not change things to discourage that. If you want total >> isolation, use Docker, don't mess with environment variables like >> this... >> >> I realize that this might just get closed due to philosophical >> differences. How about just document PYTHONUSERBASE in our FAQ or >> something (like it is in python) and trust users to have a clue? >> >> I've made https://trac.sagemath.org/ticket/21456 about this. However, >> the authors of the new code in Sage that sets PYTHONUSERBASE if it >> isn't set, might have a very different opinion, and for a good reason. >> Thoughts? >> >> -- William >> >> >> -- >> William (http://wstein.org) > > -- > 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.