[Numpy-discussion] Style for pad implementation in 'pad' namespace or functions under np.lib
Charles R Harris
Thu Mar 29 11:45:35 CDT 2012
On Thu, Mar 29, 2012 at 10:38 AM, Nathaniel Smith <firstname.lastname@example.org> wrote:
> On Thu, Mar 29, 2012 at 5:13 PM, Travis Oliphant <email@example.com>
> > While namespaces are a really good idea, I'm not a big fan of both
> > namespaces and underscore namespaces. It seems pretty redundant to me
> > have pad.pad_mean.
> > On the other hand, one could argue that pad.mean could be confused with
> > calculating the mean of a padded array. So, it seems like the function
> > names need to be called something more than just "mean, median, etc."
> > Something like padwith_mean, padwith_median, etc. actually makes more
> > Or pad.with_mean, pad.with_median. The with_ in this case is not
> > a "namespace" it's an indication of functionality.
> Perhaps it should be
> pad(..., mode="mean")
> , mode="" is only a few more characters than _with_, and this would
> make it much easier to write functions whose API looks like:
> wavelet_decompose(..., pad_mode=....)
> Also it would solve the namespace question :-).
I like this idea. I'd leave the current functions in the module for those
who want to import a particular padding type, but import the pad(...,
mode="xxx") into the numpy namespace.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion