+1 On Sat, May 31, 2008 at 5:15 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Jun 1, 1:02 am, "William Stein" <[EMAIL PROTECTED]> wrote: >> On Sat, May 31, 2008 at 3:56 PM, Gary Furnish <[EMAIL PROTECTED]> wrote: >> >> > 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. >> >> Yes, misc.functional is a very very old "dumping ground" file, where I put >> stuff that I wanted to call with functional notation (instead of >> object-oriented >> method notation). So I'm not surprised a lot of it is not irrelevant and >> not even imported to sage.all. > > Ok, so I am concluding the same thing as William and would be more > specific about depreciation procedures only for functions imported per > default. Anything that is broken and has been broken for a while > should just be removed. > > Thoughts? > >> William > > 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 -~----------~----~----~----~------~----~------~--~---
