#18558: Test all installed optional packages by default
-------------------------------------+-------------------------------------
Reporter: ncohen | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.8
Component: doctest framework | Resolution:
Keywords: | Merged in:
Authors: Nathann Cohen, | Reviewers:
Jeroen Demeyer | Work issues:
Report Upstream: N/A | Commit:
Branch: u/jdemeyer/18558 | 59af6983b05b6581ef1282cdec41d6e63ad82459
Dependencies: #18456, #18124, | Stopgaps:
#18559, #18563 |
-------------------------------------+-------------------------------------
Comment (by ncohen):
> Maybe... I think instead I am imagining that Sage could detect whether
the latest version (for a given version of Sage) was installed. R does
this all the time.
Detecting whether "the local version of a package" is the latest available
can be done easily from the output of `sage-list-package` (see #18456).
If what you want is to automatically detect, in doctests or when running
Sage, that some errors are caused by an old version of a package, then it
is a more complicated problem and you could help make this conversation
more constructive by describing a specific behaviour that you would like.
It is my belief that it is also, in this case, unrelated to this ticket.
> Yes, or something analogous to that. After all, aren't the current
package numbers already in `build/pkgs/pkg_name/version` or something? It
could just check that the packages which are installed match. (Not
necessarily for old-style, but that is presumably yet another snag.)
We can know the version of any installed packaged, be it new or old. See
output of `sage -installed` in #18456. Detecting this is not a problem.
> The only reason I think it belongs on this ticket is because this ticket
would expose the problem.
This ticket cannot fix all the pre-existing bugs that it exposes. If
everybody comes and say "this bug existed before, you must fix it or your
code will not pass" I will give up very quickly.
> 1. User occasionally runs doctests because is told it's a good idea to
make sure their Sage works.
Jeroen made sure that all tests will pass. So that's not a problem.
> 1. User updates Sage but not some package they use, because that wasn't
announced somewhere they saw it (git logs are not announcements)
For new-style packages this is already done automatically.
> 1. User runs doctests and gets mysterious failures that seem to be
related to updating Sage, but are actually related to not updating
package.
Again, only happens for old-style packages. Convert them to new-style to
avoid this problem.
> Without this ticket, that is much less likely to happen, since the
person would have to be running optional doctests - and I would agree that
such a person is not so likely to be a beginner. But that's not what
would happen here.
>
> Anyway, if two people (e.g. you and Jeroen) feel like it's not worth
dealing with here (and it probably would be a big change) I won't complain
further, except to say "I told you so" if it happens and to be very happy
if it turns out it doesn't. I did want to make sure it got raised,
though.
Thank you for your contribution. As you will see from looking at the logs,
Jeroen installed all optional doctests to make sure that all tests will
pass.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18558#comment:92>
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.
