[issue1590864] import deadlocks when using PyObjC threads

Brett Cannon added the comment: Been thinking about it and as a compromise to people who view this as a bug I am re-opening it but lowering the priority. -- components: +Interpreter Core -Library (Lib) priority: normal -> low resolution: wont fix -> stage: committed/rejected -> test ne

[issue1590864] import deadlocks when using PyObjC threads

ayal baron added the comment: Hi, We have the same problem while running two threads where one is running a subprocess command and the other is importing modules. This will cause a deadlock and this IS a bug!!! This happens quite often on a slow machine (once every 2-3 runs). -- nosy:

[issue1590864] import deadlocks when using PyObjC threads

Brett Cannon added the comment: First, because os is such a common module that hiding some uncommon imports at the module level helps with startup costs. Second, this is not a bug as the code is not behaving in an improper manner. The import lock is doing what it is supposed to be doing and imp

[issue1590864] import deadlocks when using PyObjC threads

Ronald Oussoren added the comment: I don't understand why the function-level imports cannot be removed. Wouldn't it be possible to do something like this: from errno import ENOENT as _ENOENT, ENOTDIR as _ENOTDIR def _execvpe(file, args, env=None): pass # Use _ENOENT and _ENOTDIR in this cod

[issue1590864] import deadlocks when using PyObjC threads

Brett Cannon added the comment: It seems the import lock is being triggered because of an import being made in a function call by something else being imported. And because it is the os module one can't pull out the function-level imports without causing problems. Closing as "won't fix". -

[issue1590864] import deadlocks when using PyObjC threads

Changes by Daniel Diniz : -- assignee: -> brett.cannon nosy: +brett.cannon versions: +Python 2.6 -Python 2.5 ___ Python tracker ___ ___