#10176: ImportError: No module named sagenb on openSUSE
------------------------------+---------------------------------------------
Reporter: mpatel | Owner: jason, was
Type: defect | Status: needs_info
Priority: blocker | Milestone: sage-4.6
Component: notebook | Keywords:
Author: Leif Leonhardy | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:44 jason]:
> Replying to [comment:43 leif]:
> > Replying to [comment:38 mpatel]:
> > > If I run `easy_install pep8` in a Sage subshell, the relative path
to sagenb in `easy-install.pth` is made absolute again. Does anyone else
see this?
> >
> > Of course. This will happen each time {{{easy_install}}} modifies that
file, also when (re)installing other spkgs that use setuptools.
>
>
> Wow, this seems like it is really turning into a mess. Maybe we should
just pretend to install in the normal place (the site-packages directory)
and then move that directory to the SAGE_DEVEL directory and create a
relative symlink from site-packages/sagenb... to SAGE_DEVEL/sagenb
ourselves?
As said on the IRC, I don't think this works with (at least our current)
unpatched setuptools; these expand symbolic links such that if I create
{{{
local/lib/python/site-packages/sagenb -> ../../../../devel/sagenb
}}}
and add `./sagenb` to `easy-install.pth`, installing different spkgs using
setuptools again replaces this by an absolute path.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10176#comment:48>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
