Antoine Pitrou added the comment: > However, I'm wondering if it might still be possible to avoid the > need for a thread local context to handle the combination of > expected failures and subtests when we have access to the test > caseby adding the annotation that I expected to be there in the > first place.
But that would break use cases where you use @expectedFailure on a function called by the test method, not directly on the test method itself. I don't really care about those use cases myself, but not breaking them is the reason I chose not to change the @expectedFailure implementation. I'll let Michael decide :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16997> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
