Tim Peters wrote: ... > It's trying to resolve self.J in the callback at the time it dies. Unlike > Jim's scenario, the failure here is due to that II is an insane state (the > class containing the callback code, not some other class) -- but close > enough for me. This is exactly like my scenario. The class containing the callback is hosed. In my scenario, I wasn't resuurecting anything though. Jim -- Jim Fulton mailto:jim at zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4