> I doubt if this can be automated, but if coders and reviewers are reminded > often that might help.
If we do nothing to ensure that all Sage functions will progressively be udpated, or that we have a deterministic way to check what is left to do (like for sage -coverage), then we will end up with a standard that we try to enforce but that we cannot assume in our code (i.e. assume that every integer has a .factor() attribute) and we will have to keep on importing the methods manually. If, on the other hand, we assume that standard when it is not the case in practice, we will probably break a lot of code that is not already doctested. What about *input* integers? I have many functions that take integers as input. Will the new standard enforce that those must be Integers too? If this is the case, then not only "return 1" gets forbidden, but also "my_function(1)". Nathann -- 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.
