Title: Expose `capture_locals` parameter in `traceback` convenience functions
Type: enhancement Stage:
Components: Library (Lib) Versions: Python 3.8
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: fhackdroid, r.david.murray, ulope
Priority: normal Keywords:

Created on 2018-06-08 15:52 by ulope, last changed 2018-06-21 15:33 by fhackdroid.

Messages (4)
msg319079 - (view) Author: Ulrich Petri (ulope) * Date: 2018-06-08 15:52
Since 3.5 the internal machinery of the `traceback` module has gained the very useful ability to capture locals.

It would be useful to also expose that ability through the various convenience functions.
msg319809 - (view) Author: Farhaan Bukhsh (fhackdroid) * Date: 2018-06-17 08:47
Hey, I would like to work on this, where do I start or how can I help?
msg320176 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2018-06-21 13:11
I think we should get one or more of the core devs who were involved in the changes that added that parameter to sign off on whether this is a good idea or not (I have no opinion at the moment).  You should be able to find them via git blame and looking at the issues related to the changesets you find.  Unless someone who remembers comes along and just adds them to nosy :)
msg320191 - (view) Author: Farhaan Bukhsh (fhackdroid) * Date: 2018-06-21 15:33
Hahah! Let me try to put this on the IRC channel may be someone can help us there.
Date User Action Args
2018-06-21 15:33:09fhackdroidsetmessages: + msg320191
2018-06-21 13:11:26r.david.murraysetversions: - Python 3.5, Python 3.6, Python 3.7
nosy: + r.david.murray

messages: + msg320176

type: enhancement
2018-06-17 08:47:05fhackdroidsetnosy: + fhackdroid
messages: + msg319809
2018-06-08 15:52:20ulopecreate