[sage-devel] *less* visible stopgap (i.e. wrong result warning)

2015-03-09 Thread Nathann Cohen
Hello everybody, This post is meant to keep everybody updated on what is being done in #17898 [1]. See also the previous sage-devel thread [2]. The problem: Because a function named IntegerListsLex returns wrong results [5] and does not check its input, a stopgap [3] was added in #17548

Re: [sage-devel] *less* visible stopgap (i.e. wrong result warning)

2015-03-09 Thread Jeroen Demeyer
I added some more bugs to #17548 which should convince everybody that the stopgap is still very much justified. -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-devel] *less* visible stopgap (i.e. wrong result warning)

2015-03-09 Thread Robert Bradshaw
+1 If it's too difficult to verify the input meets the preconditions in IntegerListsLex itself, we could have an optional argument (defaulting to False) that one can call to make the assertion that one knows the preconditions are met and suppresses this warning. On Mon, Mar 9, 2015 at 7:06 AM,