[issue1705520] API for excluding methods from unittest stack traces

Serhiy Storchaka added the comment: What to do with comprehensions and classes? Corresponding code objects are not easily accessible and they do not have corresponding function. It would be difficult to use the locals of the frame with comprehensions. Maybe use per-module registries of qualn

[issue1705520] API for excluding methods from unittest stack traces

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue1705520] API for excluding methods from unittest stack traces

Changes by R. David Murray : -- nosy: +Julian stage: test needed -> needs patch versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ ___

[issue1705520] API for excluding methods from unittest stack traces

Michael Foord added the comment: Global registry of code objects, hmmm... Could work. I'll prototype it and test it with IronPython / Jython / pypy. -- ___ Python tracker ___

[issue1705520] API for excluding methods from unittest stack traces

Amaury Forgeot d'Arc added the comment: Maybe a global registry... implemented with a WeakKeyDictionary? -- nosy: +amaury.forgeotdarc ___ Python tracker ___ __

[issue1705520] API for excluding methods from unittest stack traces

Michael Foord added the comment: So from the stackframe you can only get to the code object not to the function object and although the code object is also reachable from a decorator it isn't mutable so we can't "mark it" in any way. We could in theory 're-build' the function and create a new

[issue1705520] API for excluding methods from unittest stack traces

Changes by Dave Malcolm : -- nosy: +dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1705520] API for excluding methods from unittest stack traces

Michael Foord added the comment: __unittest needs to die (with appropriate deprecation). I agree that a nicer API for marking functions and methods as needing to be excluded from unittest stacktraces would be useful. A decorator is a good way to expose that API to developers. Internally unitt