add support for SAGE_PYTHONPATH
>
> > On Aug 6, 9:33 am, Rupert <rupert.n...@gmail.com> wrote:
> >> Hello there,
>
> > Hi Rupert,
>
> >> I installed sage this morning and am doing some testing. I noticed
> >> that sage was ignoring some python modules that live in a directory on
> >> my PYTHONPATH environment variable.
>
> >> Looking in $SAGE_ROOT/local/bin/sageenv, I see that it completely
> >> overrides my $PYTHONPATH, rather than prepending its own directories.
>
> > Yes, we do that on purpose.
Hi,
> I propose offering a workaround, e.g.,
> SAGE_PYTHONPATH
> which *does* get appended to PYTHONPATH
> on startup.
That sounds reasonable to me.
> Note that this is for picking up *user* code, so
> it makes a huge amount of sense to support this.
> It's not an issue of systemwide python being
> different than Sage's at all.
Well, people will use it to have Sage pick up the extensions of the
system Python, but then I get to tell you "I told you so" :)
Add something to sageenv that does what is described above.
Also add something to the README.txt that documents this behavior.
Change History (15)
Summary: 
add support for SAGE_PYTHONPATH →
[with patch, needs review] add support for SAGE_PYTHONPATH

Summary: 
[with patch, needs review] add support for SAGE_PYTHONPATH →
[with patch, needs work] add support for SAGE_PYTHONPATH

Report Upstream: 
→ N/A

Summary: 
[with patch, needs work] add support for SAGE_PYTHONPATH →
add support for SAGE_PYTHONPATH

Status: 
needs_work →
needs_info

Milestone: 
sage5.11 →
sage5.12

Milestone: 
sage6.1 →
sage6.2

Milestone: 
sage6.2 →
sage6.3

Milestone: 
sage6.3 →
sage6.4

Milestone: 
sage6.4 →
sageduplicate/invalid/wontfix

Status: 
needs_info →
needs_review

Status: 
needs_review →
positive_review

Resolution: 
→ invalid

Status: 
positive_review →
closed

This would be very nice for SageTeX, so that the user could put sagetex.py somewhere and use $SAGE_PYTHONPATH to help Sage automatically find the module.