TurboGears2 and pytest conflict about tg2

[amol-]

Given the pretty uncommon chances that a StackedObjectProxy is used as a callable and the even less common chances that it gets decorated, I think that 77132ba is a reasonable work-around to the problem.

I hoped that removing __call__ support from the object would have solved the issue, but it seems that unwrap doesn't check that what is being provided is a callable at all.

[kiilerix]

Yeah, that seems like an OK way to avoid the problem. Thanks.

1. Considering that AttributeError usually has args[0] like module 'os' has no attribute 'foo', perhaps use something more helpful than just foo. Perhaps something as no 'context' has has been registered for this thread and there is thus no attribute 'foo'.

2. But this also leads to the question of whether it just always should fail with AttributeError instead of TypeError.

3. If not always returning AttributeError, then perhaps do it for all __ methods - not just __wrapped__.

4. Can you recommend a workaround for using pytest doctest with existing TG2 versions?

[amol-]

Probably going for all dunder methods makes sense. I'll update the patch.

Regarding how to avoid problem with current version. I think that the issue comes from the fact that it's exploring all variables exposed in modules or something like that. Maybe changing from tg import request to things like import tg and then using tg.request instead of just request might fix the issue.
A similar issue has also been reported for Flask (who uses threadlocal objects too) with pytest a few times, even though I think it's the first time I see it in the context of doctest.