Re: [sage-devel] Re: [sage-combinat-devel] Re: Order of Partitions()

2015-03-18 Thread Jeroen Demeyer
On 2015-03-18 12:40, Mike Zabrocki wrote: (at least for values less than 15) I really don't like that defaults would depend on the input size. Somebody working with small examples might *assume* that the order is in a given way, and then suddenly his code will break down on larger examples. -

Re: [sage-devel] Re: [sage-combinat-devel] Re: Order of Partitions()

2015-03-18 Thread Jori Mantysalo
On Wed, 18 Mar 2015, Jeroen Demeyer wrote: So would it make sense to have an optional parameter sorted=None, which one could set to 'lex' or 'revlex' to get them in a desired order. The documentation could warn about the issues you just raised. If there is a general agreement on this, I could

Re: [sage-devel] Re: [sage-combinat-devel] Re: Order of Partitions()

2015-03-18 Thread Jeroen Demeyer
On 2015-03-18 09:20, Samuel Lelievre wrote: So would it make sense to have an optional parameter sorted=None, which one could set to 'lex' or 'revlex' to get them in a desired order. The documentation could warn about the issues you just raised. If there is a general agreement on this, I could

Re: [sage-devel] Re: [sage-combinat-devel] Re: Order of Partitions()

2015-03-17 Thread Jeroen Demeyer
I think that for *most* applications the order does not matter, so I would vote on not sorting by default. If you need sorting, just do it yourself (or use IntegerListsLex). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from thi