[Numpy-discussion] Style for pad implementation in 'pad' namespace or functions under np.lib

[Charles R Harris]

On Thu, Mar 29, 2012 at 10:38 AM, Nathaniel Smith <njs at pobox.com> wrote:

> On Thu, Mar 29, 2012 at 5:13 PM, Travis Oliphant <travis at continuum.io>
> wrote:
> > While namespaces are a really good idea, I'm not a big fan of both
> "module"
> > namespaces and underscore namespaces.   It seems pretty redundant to me
> to
> > 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
> sense.
> >   Or pad.with_mean, pad.with_median.   The with_ in this case is not
> really
> > 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.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20120329/6a879104/attachment.html>