#10176: ImportError: No module named sagenb on openSUSE
------------------------------+---------------------------------------------
Reporter: mpatel | Owner: jason, was
Type: defect | Status: needs_work
Priority: blocker | Milestone: sage-4.6.1
Component: notebook | Keywords:
Author: Leif Leonhardy | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:56 jdemeyer]:
> Replying to leif:
> > Just curious: *Which* 'sage' is supposed to be called here?
> > Should we check if SAGE_LOCAL or SAGE_ROOT is defined?
> > ... and perhaps call $SAGE_ROOT/sage or $SAGE_LOCAL/bin/...?
>
> I think it's not important which `sage` is called. It just needs `sage
-pkg`, `sage -hg` and so on to do the Right Thing.
;-) Well, since SageNB moved from a more or less typical spkg to something
more like the Sage library, I expect more people - potentially less
familiar with the SageNB update process - to work on it.
So it's now IMHO more likely developers will have a broken (or outdated)
Sage in their default path (i.e., outside a Sage subshell), in which case
"arbitrary" things could happen.
If `sage-env` was sourced, i.e. some variables like `SAGE_LOCAL` or
`SAGE_ROOT` are defined*, we can perhaps be more sure `sage` is the
"proper" one, i.e. more recent.
----
* I prefer having `SAGE_ENV_SOURCED` anyway, to also avoid to
(effectively) source it more than once. See #10469.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10176#comment:59>
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.
