On 4/4/07, Andrew Straw <[EMAIL PROTECTED]> wrote: > Do we add deprecation warnings for the 0.90+1 release cycle and then > stop building the numarray and numeric numerix backends at some point > after that? When? Do we keep the "numerix" name or just switch > everything to numpy?
I agree that it is about time to begin preparing for the switch. I was talking to Perry the other day about what an irony it was for him when he was writing the colormap support in mpl that he had to use all the takes and puts after spending so much effort in numarray to get more natural indexing and other features. So I think most everyone is ready to jettison the old stuff and move forward with the new. I've been waiting for the green light from STScI that they are mostly finished with their numarray->numpy migration since they have made significant contributions to mpl (and numerix) and if I recall correctly, I think Perry said they were mostly done, which means we should go forward. Perry? As for your specific points: * inside matplotlib we should just use numpy everywhere. We need to agree on some import convention. I'm happy with 'import numpy as nx' though this might be confusing for a while since people might confuse it with the numerix layer. I like nx because numpy is too long, and N occurs too frequently in regular code. I don't like capital letters.... I could see ns too, since that is what we have been using for the numpy extensions when numpy was originally discussed in the context of the scipy core. * I suppose we should deprecate it for a release, but I'm inclined just to push the thing through quickly because it is a big change and if and when we have energy for it we should just get it done. I'm also happy to have some sense talked into me. I suppose one possibility is to deprecate it *now* and push out 0.91 ASAP and then immediately pull the old support out. I'll post on user's list to get a sense of how many people both need the latest mpl and the older array packages. I can't imagine there are too many... I'm sure some people need Numeric or numarray, but if they are that curmudgeonly, surely they can live on the older mpl branch. * I would like to see the numerix layer live on, not for use in mpl but for use outside it for folks who have written a lot of code around it in external scripts. So people who have done from pylab import nx or import matplotlib.numerix as nx will still have working code. Of course we will lose all the mpl extensions compiled against the other array packages, but with the array interface I don't think this will pose a problem for people using mpl with recent versions of Numeric or numarray * when we do the cleanup, we should replace all the 'from numerix import something' with 'import numpy as nx; nx.something' as above. Where possible when cleaning a given module for numerix, we should standardize the other imports. Eg, instead of 'from cbook import iterable' we should do 'import matplotlib.cbook as cbook; cbook.iterable' Let's use this convention where we use absolute imports renamed to relative imports, and qualify all module functions in the code with the module names. Anything else? JDH ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
