#17898: Removal of wrong stopgap
-------------------------------------+-------------------------------------
Reporter: aschilling | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.6
Component: combinatorics | Resolution:
Keywords: stopgap, | Merged in:
partitions | Reviewers: Travis Scrimshaw,
Authors: Travis Scrimshaw, | Anne Schilling
Anne Schilling | Work issues:
Report Upstream: N/A | Commit:
Branch: | 2f7a90d8419ca8d2202b3cb31290e58194f666e3
public/combinat/fix_bad_stopgap-17898| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by aschilling):
Hi Nathann,
You agreed that it is very damaging to Sage that a message pops up in many
use cases where there is no bug known saying "This code contains bugs and
may be mathematically unreliable." The message of the stopgap is also not
informative at all saying that this is related to IntegerListsLex. If
someone uses Partitions or crystals and this message pops up, they will
think it is related to their object, which it is not.
Since this is really a User input issue (and no bugs seem to be known in
the valid input range), I think the implemented solution is the best. Also
note that the stopgap message does not show up when running tests on the
sage tree. Hence your desire to have this message pop up in all cases
anyway does not seem to apply for developers (who run tests).
Anne
--
Ticket URL: <http://trac.sagemath.org/ticket/17898#comment:26>
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.
