The things in misc.functional are covered up by other imports in general. They only are usable if you change the import order in all.py in major ways, and no other code in Sage uses them. In fact there is code in there that is not doctested that doesn't even work. In general I agree with you, but in this specific case I believe this is 100% safe.
On Sat, May 31, 2008 at 4:40 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > On Jun 1, 12:27 am, "Gary Furnish" <[EMAIL PROTECTED]> wrote: > > Hi Gary, > >> A bunch of the stuff in misc.functional is junk... I've deleted a >> bunch of it in my symbolics rewrite without any issues. > > You because you didn't have any problem there does not mean we can > just delete things willy-nilly. I would very strongly recommend that > we write down some deprecation procedure and make it mandatory that > such procedures are followed. If you remove some function now and a > months from now somebodies code breaks because we removed something > now and the person did either skip a couple upgrades or did not read > all the details in the release notes *we developers* look like idiots > for breaking the code. Now if it printed warnings per default for the > next six months and then was removed I am 100% fine with that. > > And I am not talking about some "what if situation", but > > "#3253 f.jacob() used to work to compute jacobian ideal. Now it > doesn't" > > illustrates the problem. The jacob() function was renamed in 2.10.3 to > gradient(), but in 3.0.2 somebody noticed that his old code was broken > all the sudden. > > <SNIP> > > Cheers, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
