On Tue, Mar 15, 2011 at 5:41 AM, Charles R Harris <[email protected]> wrote: > > > On Sun, Mar 13, 2011 at 5:01 AM, Ralf Gommers <[email protected]> > wrote: >> >> On Sun, Mar 13, 2011 at 1:57 PM, David Warde-Farley >> <[email protected]> wrote: >> > >> > On 2011-03-12, at 9:32 PM, Charles R Harris wrote: >> > >> >> I'd like to change the polynomial package to only import the Classes, >> >> leaving the large number of implementation functions to be imported >> >> directly >> >> from the different modules if needed. I always regarded those functions as >> >> implementation helpers and kept them separate from the class so that >> >> others >> >> could use them to build their own classes if they desired. For most >> >> purposes >> >> I think the classes are more useful. So I think it was a mistake to import >> >> the functions by; default and I'm looking for a graceful and acceptable >> >> way >> >> out. Any suggestions. >> >> How about just deprecating in 1.6 and removing from the polynomial >> namespace in 2.0? Then you do need to add to the docs explicitly that >> the submodules contain these functions, that they are part of the >> public API and are not going anywhere. >> > > Is there a clever way to deprecate the functions only in that namespace? I > wrote a script that writes a lot of dummy functions that call the original > with a deprecation message, but I'd sure welcome a cleaner way to do things.
Seems clean to me if you're using numpy.deprecate for it. Can you commit that today? Ralf _______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
