[issue1755179] Deadlocks with fork() and multithreading

2008-01-07 Thread Facundo Batista
Facundo Batista added the comment: Backported, commited in r59823. -- resolution: - fixed status: open - closed _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1755179 _

[issue1755179] Deadlocks with fork() and multithreading

2007-11-27 Thread Facundo Batista
Facundo Batista added the comment: Fixed in the trunk, rev 59195. _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1755179 _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1755179] Deadlocks with fork() and multithreading

2007-11-27 Thread Georg Brandl
Georg Brandl added the comment: Will it be backported? -- nosy: +georg.brandl _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1755179 _ ___ Python-bugs-list

[issue1755179] Deadlocks with fork() and multithreading

2007-11-23 Thread Christian Heimes
Christian Heimes added the comment: It sounds like the importer dead lock problem. These problems are almost impossible to unit test because they are usually race conditions. I don't see a problem in moving the import to the module name space. errno is a built-in module and the import isn't

[issue1755179] Deadlocks with fork() and multithreading

2007-11-01 Thread Facundo Batista
Facundo Batista added the comment: I followed the link you provided. All the discussion there ends asking for a realiable way to test the problem (otherwise, we could be making more mistakes than solving the problem in the different platforms). Please provide a test case, so we include it in

[issue1755179] Deadlocks with fork() and multithreading

2007-10-23 Thread Facundo Batista
Changes by Facundo Batista: -- assignee: - facundobatista nosy: +facundobatista _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1755179 _ ___ Python-bugs-list