Hi Todd,
I agree a flag is more suitable than classes.
I would add another bonus of a flag than a function argument is to avoid
massive contamination of function signatures for a global variation of
behavior that affects many functions.
Yu
On Wed, Jan 9, 2019 at 11:34 PM Todd wrote:
> On Mon,
constants are easier to support for autocompletion than strings. My
current env (emacs) will (usually) autocomplete the former, but not the
latter.
On Thu, Jan 10, 2019 at 2:21 PM Feng Yu wrote:
> Hi Todd,
>
> I agree a flag is more suitable than classes.
>
> I would add another bonus of a flag
> On 10 Jan 2019, at 6:35 pm, Todd wrote:
>
> Could this approach be used to deprecate `ravel` and let us just use
> `flatten`?
Could we not? `.ravel()` is everywhere and it matches `ravel_multi_index` and
`unravel_index`.___
NumPy-Discussion mail
On Wed, Jan 9, 2019 at 10:55 PM Eric Wieser
wrote:
> Slicing is a lot more important than some keyword. And design-wise,
> filling the numpy namespace with singletons for keyword to other things in
> that same namespace just makes no sense to me.
>
> At least from the perspective of discoverabili
On Thu, Jan 10, 2019 at 11:21 AM Feng Yu wrote:
> Hi Todd,
>
> I agree a flag is more suitable than classes.
>
> I would add another bonus of a flag than a function argument is to avoid
> massive contamination of function signatures for a global variation of
> behavior that affects many functions
