On Tue, Apr 22, 2003, Jeremy Hylton wrote: > > Abstract > ======== > > This PEP describes a mechanism for attaching profile and trace > functions to a thread when it is created. This mechanism allows > existing tools, like the profiler, to work with multi-threaded > programs. The new functionality is exposed via a new event type for > trace functions. Hrm. While I don't want to overload what looks like a simple PEP, I'd like some thoughts about how this ought to interact with thread-local storage (if at all). There are some modules (notably the BCD module) that need to keep track of state on a per-thread basis, but without requiring a user of the module to do the work. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ Why is this newsgroup different from all other newsgroups?
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