This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Warnings stacklevel frames to skip
Type: enhancement Stage: needs patch
Components: Library (Lib) Versions: Python 3.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Jim.Jewett, jayvdb
Priority: normal Keywords:

Created on 2015-09-22 15:47 by Jim.Jewett, last changed 2022-04-11 14:58 by admin.

Messages (2)
msg251328 - (view) Author: Jim Jewett (Jim.Jewett) * (Python triager) Date: 2015-09-22 15:47
warnings.warn(stacklevel=2) is a longstanding idiom.

It broke in 3.3 because python itself added some additional infrastructure frames in between; now stacklevel should be 8 or 10 in some releases.

issue24305 adds a workaround for 3.5, to ignore internal frames -- defined as those which contain both 'importlib' and '_bootstrap' in filename.

I would prefer to see a supported hook, so that either the caller or the program setup could list other modules or packages to ignore when counting frames.  That way, I could write

mycall(otherlib(foo))

and otherlib could ensure that the warning pointed to mycall, rather than to something internal to otherlib, even if otherlib were refactored to a different stack depth.

Ignoring just the import machinery would of course be a good default.
msg256169 - (view) Author: John Mark Vandenberg (jayvdb) * Date: 2015-12-10 08:16
This looks a lot like the patch on http://bugs.python.org/issue850482
History
Date User Action Args
2022-04-11 14:58:21adminsetgithub: 69403
2015-12-10 08:16:01jayvdbsetmessages: + msg256169
2015-12-10 08:06:01jayvdbsetnosy: + jayvdb
2015-09-22 15:50:33Jim.Jewettsetstage: needs patch
2015-09-22 15:47:00Jim.Jewettcreate