#9507: if spkg-install is a Python script, first check that
SAGE_LOCAL/bin/python
exists.
-----------------------------+----------------------------------------------
Reporter: was | Owner: GeorgSWeber
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-4.5.1
Component: build | Keywords:
Author: William Stein | Upstream: N/A
Reviewer: Robert Miller | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by leif):
To avoid confusion to users, we should perhaps clarify in the error
message that '''''Sage's''' Python'' is not yet installed. (Otherwise I
expect reports like ''"I have a Python installed, but..."''.)
The comment should read {{{# if not, ...}}} rather than {{{# if so, ...}}}
(or {{{check if ...}}} should be negated).
I'd prefer {{{[ -x $SAGE_LOCAL/bin/python]}}}. Hope this never gets a
script (ending up in the scripts repo) that tries to call the binary
located elsewhere. On the other hand, we could do just this (making it a
bash script), and test for presence of the binary in that script. The
advantage would be that {{{env python}}} would always find Sage's one (no
matter if the binary is already installed), of course assuming {{{sage-
env}}} has been sourced. But this would also introduce another stage of
indirection...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9507#comment:5>
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.
