Re: import in threads: crashes & strange exceptions on dual core machines

Steve Holden wrote: > Klaas wrote: >> robert wrote: >> >>> Klaas wrote: >>> It seems clear that the import lock does not include fully-executing the module contents. To fix this, just import cookielib before the >>> >>> What is the exact meaning of "not include fully-executing" - >>> re

Re: import in threads: crashes & strange exceptions on dual core machines

Klaas wrote: > robert wrote: > >>Klaas wrote: >> >>>It seems clear that the import lock does not include fully-executing >>>the module contents. To fix this, just import cookielib before the >> >>What is the exact meaning of "not include fully-executing" - regarding the >>examples "import cookie

Re: import in threads: crashes & strange exceptions on dual core machines

robert wrote: > Klaas wrote: > > It seems clear that the import lock does not include fully-executing > > the module contents. To fix this, just import cookielib before the > > What is the exact meaning of "not include fully-executing" - regarding the > examples "import cookielib" ? > Do you real

Re: import in threads: crashes & strange exceptions on dual core machines

Klaas wrote: > It seems clear that the import lock does not include fully-executing > the module contents. To fix this, just import cookielib before the What is the exact meaning of "not include fully-executing" - regarding the examples "import cookielib" ? Do you really mean the import statemen

Re: import in threads: crashes & strange exceptions on dual core machines

It seems clear that the import lock does not include fully-executing the module contents. To fix this, just import cookielib before the threads are spawned. Better yet, use your own locks around the acquisition of the opener instance (this code seems fraughtfully thread-unsafe--fix that and you s