Eric,
Good point. Off we go with the warning then.
>
> The attribute name, _basedict, indicates that it is a private attribute,
> so I don't see why a deprecation warning is needed at all. Anyone using
> private attributes should also be reading release notes. I don't like
> the idea of a warning
Pierre GM wrote:
> All,
> I intend to rename a little-known attribute of MaskedArray, _basedict, to
> something more understandable such as _optinfo. This attribute is a
> dictionary that comes handy when subclassing MaskedArray or to save
> information.
> _basedict would still be available for
On Sunday 03 August 2008 16:31:33 Nathan Bell wrote:
> On Sun, Aug 3, 2008 at 1:29 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> Can you could trap it in __getattr_ instead? For instance:
> http://projects.scipy.org/scipy/scipy/browser/trunk/scipy/sparse/csr.py#L87
I could but I don't want to. Mask
On Sun, Aug 3, 2008 at 1:29 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
>
> I intend to put a DeprecationWarning at the beginning of numpy.ma.core. A
> side-effect is that this warning is issued each time numpy.ma is imported,
> which clutters the output of the tests.
> Am I missing something ?
Can y
All,
I intend to rename a little-known attribute of MaskedArray, _basedict, to
something more understandable such as _optinfo. This attribute is a
dictionary that comes handy when subclassing MaskedArray or to save
information.
_basedict would still be available for a while as an alias to _opti
