> Perhaps keep default >=0 but when new_variable is called issue > DeprecationWarning that the default will change? New parameters should allow > setting both >=0 and free explicitly, so that those who want >=0 in the > future can set it now and those who don't can also set it now, and when the > default will change - no code will be broken, just some of it will explicitly > set a parameter which is there by default anyway, which is not that big of a > deal. > > get/set methods on the other hand can just be deprecated directly.
Hmmm.. Well, indeed new_variable could give a warning whenever the future "min" argument is left undefined. Makes sense. Though p['x'] call new_variable implicitly. Hmmmmmm.. Okay okay, this way works. 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/groups/opt_out.
