You almost certainly need to 1) wrap that in something that catches the deprecation warning, and 2) add a deprecation warning to all methods of verbose (as the user will not see the one in the ctor (unless he decides to build his own instance of Verbose)).

I get the deprecation warning with

frommatplotlibimportverbose

Not good enough?

you probably get it with just "import matplotlib" no?...

Oh goodness I hope not.

If so hints on wrapping appreciated.

Just wrap all methods manually too.
There's no (practical) way in which you can trigger a warning when people just access the object from the module without interacting with it in any way (well see njsmith's metamodule for example for a solution, not that I suggest to use this here), but that's the same situation as when we're deprecating e.g. functions (the warning only occurs when you call the function) and we just accept that as being good enough.

I didn't realize it when we had the RC's, but I think this broke PyCharm's support for embedding figures.

Not to make this any worse or anything. 😉

OK, well, this is a bit out of my depth.

importmatplotlib

indeed triggers the deprecation warning if I have in__init__.py:

# define verbose so it can be imported...verbose=Verbose()

I don't know how to turn that warning off and still assignverbose.

OK< think I got it.

importmatplotlibfrommatplotlibimportverbose

issues no warnings. But

verbose.report('Boo')

does....

Looks like this can go in after a rebase.

@dopplershift this is a good example of a mysterious failing codecov/project/tests.

Because macOS builds didn't upload any coverage...

Ahhhh. Cool. Thanks!

I think something went wrong with the rebase as this does not actually butverbose back any more....