Code

Changes between Initial Version and Version 1 of Ticket #21024


Ignore:
Timestamp:
09/03/13 05:51:43 (8 months ago)
Author:
aaugustin
Comment:

#21025 was a duplicate.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21024 – Description

    initial v1  
    33This includes how to silence deprecation warnings: 
    44 
    5 When a feature is deprecated, it raises a `PendingDeprecationWarning`, either at import time or at run time. After the following release it raises `DeprecationWarning`. Assuming we have a good test coverage, these warnings will be shown by the test suite, with `-Wall` for `PendingDeprecationWarning`, or by default for `DeprecationWarning`. This is annoying. The output of the test suite should remain clean. 
     5When a feature is deprecated, it raises a `PendingDeprecationWarning`, either at import time or at run time. After the following release it raises `DeprecationWarning`. Assuming we have a good test coverage, these warnings will be shown by the test suite, with `-Wall` for `PendingDeprecationWarning`, or by default for `DeprecationWarning`. This is annoying. The output of the test suite should remain clean. 
    66 
    77Aymeric's full post including how to silence warnings: