Grokking a module that is using unititialized paste.registry.StackedObjectProxy objects fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grok |
New
|
Undecided
|
Martijn Faassen |
Bug Description
Paste has StackedObjects that when unititialized are giving out Type errors on failed getattrs. So when grokking a Pylons application:
File "/home/
reverse=True)
File "/home/
if not util.defined_
File "/home/
obj_module = getattr(obj, '__grok_module__', None)
File "/home/
return getattr(
File "/home/
'thread' % self.____name__)
TypeError: No object (name: request) has been registered for this thread
I understand this is a nasty thing for paste StackedObjectProxy to do, but I don't have a choice really, because Pylons are using Stacked objects heavily. So maybe it would be possible to handle it on the grok side?
At the moment the workaround is to "stacked_
Does martian needs his own launchpad entry?