#16702: Raise exceptions when database_gap is not installed
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-6.3
enhancement | Resolution:
Priority: major | Merged in:
Component: group | Reviewers:
theory | Work issues:
Keywords: | Commit:
Authors: | 2dbb38d2d5d528971fde504390f903d42969f6ff
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
u/ncohen/16702 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by dimpase):
Replying to [comment:3 ncohen]:
> I copy/pasted the test which is already used for gap_packages.
have you ever noticed that Sage is full of crappy code, in some places at
least ?
;-)
> Plus you don't have any way to differentiate exceptions originating from
a gap code I guess. If you try/catch you could catch too much and say that
the package is not installed when something else is going wrong.
I am not saying that inside the exception processing block you should not
test for installation of this package.
But without `try` your patch is too intrusive.
There are ways to extend GAP and/or Sage in place not involving installing
Sage packages...
--
Ticket URL: <http://trac.sagemath.org/ticket/16702#comment:4>
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.
