Hi, and happy new year!
I wonder under what conditions there should be a deprecation warning
before removing a method: Can one do without a deprecation warning, if
the method does not really provide an apparent functionality? Or would
we argue: It is theoretically possible that some third-party
Dear sage-devel,
A while back we decided that we shouldn't just randomly break users'
existing code even if the reason is very good (e.g. there are 20 names
for the exact same thing, and 19 of them are just bad, or we want to
change to a better convention for something). The idea was that