On Apr 6, 2011, at 9:36 AM, pierreth wrote: > >> Going down that road, rather than rebinding sys.path to a thread-local >> version, what if we added a thread-local member to sys.path that pointed to >> the current application's modules directory? That'd be *really* simple, >> again if I'm not missing something. > > I thought about it but a thread-local variable is not a string so we > cannot add it to sys.path. So it is a problem.
Indeed. I thought I might be missing something, and that's it: the perennial problem with thread-local constructs.
