How can I figure out what line of Python code is generating a PendingDeprecationWarning?

Question

I have a set of Python 3 unittests, which, when executed with this command line:

python3 -m unittest discover -f -v

...are generating a PendingDeprecationWarning:

/usr/local/Cellar/python3/3.4.2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/imp.py:32:
    PendingDeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses

Is there an easy way for me to trace which peice of code is ultimately using imp.py, perhaps by turning on some form of stack tracing? I have narrowed it down somewhat; it seems to only be triggered when I use freezegun. However, freezegun itself doesn't seem to use imp.

score 4 · Accepted Answer · answered May 25 '15 at 15:50

4

When invoking python on the command line, pass the option -Werror to it. This will turn all warnings into errors, and when the warning/error doesn't get handled, it will display a traceback that will give you line numbers and source files for each step that let to the warning/error.

answered May 25 '15 at 15:50

randomusername

7,927
23
50

1

Perfect! That helped me determine that it was the dependent library `six`. – Andrew Ferrier May 25 '15 at 15:55
FWIW, this was the bug: https://bitbucket.org/gutworth/six/issue/112/sixmovesreload_module-uses-deprecated-imp – Andrew Ferrier May 25 '15 at 16:05

How can I figure out what line of Python code is generating a PendingDeprecationWarning?

1 Answers1