On Sat, Sep 9, 2017 at 9:20 PM, Ralf Hemmecke <hemme...@gmail.com> wrote: > On 09/09/2017 05:05 PM, Maarten Derickx wrote: >> In case people start setting pythonpath after reading this thread: >> you will actually get some silly doctest failures if python path is >> set. > > I don't need to set SAGE_PATH (or PYTHONPATH) for testing Sage. All I > want is to tell Sage about a locally installed package that does not > come from "sage -i". > > As I understand what Nils was saying is that instead of SAGE_PATH I > should simply switch to PYTHONPATH directly. > > That would be OK for me. > > However, it's quite bad that the commit that removed SAGE_PATH did not > also consider to change the documentation for Sage 8.0. It still says > that SAGE_PATH is in use.
I agree--this is one of those cases where we could do better about deprecation. Even if it were imperative to change things so that SAGE_PATH were ignored completely, it would still be a better deprecation path to at least supply a warning that it's not used anymore :) -- 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.
