#19213: For packages listed in build/pkgs/piprules, allow 'sage --optional' to
list
them
-------------------------------------+-------------------------------------
Reporter: jhpalmieri | Owner:
Type: enhancement | Status: needs_work
Priority: minor | Milestone: sage-6.9
Component: scripts | Resolution:
Keywords: | Merged in:
Authors: John Palmieri | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jhpalmieri/pip_packages | 00224aafc17efcb3a4d5504bdbcf036fae5bca57
Dependencies: #19187 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jhpalmieri):
I have a few questions and comments:
- if #19220 is merged (archiving superseded packages, including the
`piprules` packages), how are users supposed to find out about
`biopython`, `brian`, etc.? We need to include an option to `sage` which
will call `sage-list-packages python`. Maybe we should also have an option
which lists all packages: first standard, then optional, then
experimental, then python/pip. Or maybe group all of the non-standard
packages together, sorted by name. In any case, we shouldn't expect users
to even be aware that there are several different types of non-standard
packages; they should instead just be able to get one list to see if some
particular package is supported.
Maybe a list like
{{{
[package (type)] .......... [latest version] ([installed version])
...
biopython (pip) ........... latest version (installed version)
...
chomp (experimental) ...... latest version (installed version)
...
ore_algebra (optional) .... latest version (installed version)
...
}}}
I'm not really sure, though.
- Regarding the versions, I am not convinced that we can accurately
specify which version of each package we support. Who is going to maintain
this? Unless there is some automatic way of determining the versions
supported by Sage, the versions will quickly get out of date. If `brian`
gets updated to 1.4.2 but we list `brian=1.4.1`, what happens if a user
does `sage -i brian`? What happens if a user does `sage --pip install
brian`?
--
Ticket URL: <http://trac.sagemath.org/ticket/19213#comment:13>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
