+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, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > 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 sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
