#16897: use pip for some optional/experimental python packages
-------------------------------------+------------------------
Reporter: vdelecroix | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.4
Component: build | Resolution:
Keywords: | Merged in:
Authors: Vincent Delecroix | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------------+------------------------
Comment (by embray):
#20218 offers a middle ground--it keeps `spkg-install` (in particular
since at least some packages need a little more work before it can run
`pip`). But for most Python packages the sole function of `spkg-install`
is to cd into its source and run `pip`.
I think having a proper `spkg-install` script for each package, even if
it's trivial, is ultimately simpler and less confusing than having
different build/install paths for different kinds of packages that meet a
very specific set up conditions. Better that all packages have an `spkg-
install` documenting "this is how you install this package", and not
require a priori knowledge that some arbitrary package happens to be a
Python module distribution.
--
Ticket URL: <http://trac.sagemath.org/ticket/16897#comment:2>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
