On Wed, Jan 9, 2019, 16:32 Sandro Tosi <[email protected] wrote: > On Wed, Jan 9, 2019 at 10:24 AM E. Madison Bray <[email protected]> > wrote: > > > > Package: matplotlib2 > > Version: 2.2.3-5 > > Severity: normal > > > > Dear Maintainer, > > > > There is a known incompatibility between the current release of > > matplotlib 2.2.3 and Numpy 1.16, which results in some > > DeprecationWarnings. In turn, this issue is affecting tests in sagemath > > in experimental, which use matplotlib, causing them to fail due to the > > unexpected DeprecationWarnings. > > DeprecationWarning are, by definition, warnings. if your code/your > package code fails because of them, you need to relax whatever check > is been executed. warnings are there to let you know things will > change in the future, they are NOT an indication of anything wrong. > > it looks to be a common practice in the "python science" packages to > threat DepWarnings as errors, this is not the correct usage. >
That's not the issue here. It's not that it's considered an error. Rather, the problem for sagemath in particular is that it has an extensive suite of doctests, and so unexpected deprecation warnings results in many failing doctests. The alternative is to silence the DeprecationWarning but that is also not desirable as we do want to know about such issues when they occur. Thanks. >
