#6538: bug in Partitions
--------------------------------------+-------------------------------------
       Reporter:  jhpalmieri          |         Owner:  mhansen       
           Type:  defect              |        Status:  closed        
       Priority:  major               |     Milestone:  sage-5.3      
      Component:  combinatorics       |    Resolution:  fixed         
       Keywords:  partitions, days38  |   Work issues:                
Report Upstream:  N/A                 |     Reviewers:  Benjamin Jones
        Authors:  Travis Scrimshaw    |     Merged in:  sage-5.3.beta2
   Dependencies:  #12925              |      Stopgaps:                
--------------------------------------+-------------------------------------

Comment (by nthiery):

 Replying to [comment:17 jhpalmieri]:
 > If you're still looking for something that gives the wrong answer, use
 `parts_in`:
 > {{{
 > sage: [len(p) for p in Partitions(10, length=6, parts_in=[1,2])]
 > [5, 6, 7, 8, 9, 10]
 > sage: Partitions(10, parts_in=[1,2]).cardinality() == Partitions(10,
 length=6, parts_in=[1,2]).cardinality()
 > True
 > }}}
 > Another ticket?
 >
 > Edit: I guess this is #12278.)

 Yup: I copy pasted this example as a comment in #12278!

 However, I was looking for an example giving wrong results while only
 using the IntegerListsLex engine (i.e. without parts_in). Thanks though
 :-)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6538#comment:18>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to