On Wed, Sep 15, 2010 at 3:34 PM, Benjamin Root wrote:
> On Wed, Sep 15, 2010 at 8:28 AM, Ralf Gommers
> wrote:
>>
>>
>> On Fri, Sep 10, 2010 at 12:05 AM, Peter
>>> http://docs.python.org/library/warnings.html#updating-code-for-new-versions-of-python
>>>
>>> This makes sense to me for deprecation
On Wed, Sep 15, 2010 at 10:34 PM, Benjamin Root wrote:
> On Wed, Sep 15, 2010 at 8:28 AM, Ralf Gommers > wrote:
>
>>
>>
>> On Fri, Sep 10, 2010 at 12:05 AM, Peter <
>> numpy-discuss...@maubp.freeserve.co.uk> wrote:
>>
>>> Hi all,
>>>
>>> NumPy currently makes extensive use of the DeprecationWarn
On Wed, Sep 15, 2010 at 8:28 AM, Ralf Gommers
wrote:
>
>
> On Fri, Sep 10, 2010 at 12:05 AM, Peter <
> numpy-discuss...@maubp.freeserve.co.uk> wrote:
>
>> Hi all,
>>
>> NumPy currently makes extensive use of the DeprecationWarning
>> class to alert users when some feature is going to be withdrawn.
On Fri, Sep 10, 2010 at 12:05 AM, Peter <
numpy-discuss...@maubp.freeserve.co.uk> wrote:
> Hi all,
>
> NumPy currently makes extensive use of the DeprecationWarning
> class to alert users when some feature is going to be withdrawn.
> However, as of Python 2.7, the DeprecationWarning is silent by
>
Hi all,
NumPy currently makes extensive use of the DeprecationWarning
class to alert users when some feature is going to be withdrawn.
However, as of Python 2.7, the DeprecationWarning is silent by
default, see:
http://docs.python.org/library/warnings.html#updating-code-for-new-versions-of-python