#17898: Removal of wrong stopgap
-------------------------------------+-------------------------------------
       Reporter:  aschilling         |        Owner:
           Type:  defect             |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-6.6
      Component:  combinatorics      |   Resolution:
       Keywords:  stopgap,           |    Merged in:
  partitions                         |    Reviewers:  Travis Scrimshaw
        Authors:  Anne Schilling     |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  b6f375ce349643dbff01ba8cb4c86ffc5a446e0e
  public/combinat/fix_bad_stopgap-17898|     Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------
Changes (by tscrim):

 * commit:  39142901893bc0207e8271ccd4772469fe958e0f =>
     b6f375ce349643dbff01ba8cb4c86ffc5a446e0e
 * branch:  public/ticket/17898 => public/combinat/fix_bad_stopgap-17898


Comment:

 Replying to [comment:17 jdemeyer]:
 > Replying to [comment:11 ncohen]:
 > > I asked in my earlier comment whether you could, instead of removing
 the stopgap, only raise it in case that have not been checked for
 correctness. I do not understand why this proposal has been ignored. To
 me, it sounds like the best way out: you would not see it in case for
 which you know the code is correct, and we would see it when there is a
 risk. Isn't it all good for everyone?
 >
 > I absolutely agree with this. Travis, if you really want to remove the
 stopgap, just implement the above!

 Why didn't either of you do so to begin with? Instead you both got us into
 this sad situation. So yet again, I had to spend my time and energy fixing
 this ridiculous stopgap in order for Sage not to look like it doesn't even
 work for simple and common combinatorial objects. I am tired of being
 forced into these things because someone wants to swing a hatchet around
 on a soapbox.

 Thus the issue is now fixed. This may not be the best way, but because
 this situation, this ticket must go in.
 {{{
 sage: P = Partitions(6, min_slope=0)
 sage: list(P)
 [[6], [3, 3], [2, 2, 2]]
 }}}
 ----
 New commits:
 
||[http://git.sagemath.org/sage.git/commit/?id=b6f375ce349643dbff01ba8cb4c86ffc5a446e0e
 b6f375c]||{{{Fix known errors and remove the appalling stopgap.}}}||

--
Ticket URL: <http://trac.sagemath.org/ticket/17898#comment:21>
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.

Reply via email to