> I'm still catching up on several hundred emails over the weekend. I > had a sneaking suspicion that infindattr wasn't thread-safe, so I'm > convinced this is a bug in the implementation. One approach might be > to store the info in the thread state object (isn't that how the > recursive repr stop flag is stored?) Whether this works depends on how exactly the info is stored. A single flag won't be sufficient, since multiple objects may have __findattr__ in progress in a given thread. With a set of instances, it would work, though. Regards, Martin
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