[issue1755179] Deadlocks with fork() and multithreading

Facundo Batista added the comment: Backported, commited in r59823. -- resolution: -> fixed status: open -> closed _ Tracker <[EMAIL PROTECTED]> _ __

[issue1755179] Deadlocks with fork() and multithreading

Georg Brandl added the comment: Will it be backported? -- nosy: +georg.brandl _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list ma

[issue1755179] Deadlocks with fork() and multithreading

Facundo Batista added the comment: Fixed in the trunk, rev 59195. _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscri

[issue1755179] Deadlocks with fork() and multithreading

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 cost

[issue1755179] Deadlocks with fork() and multithreading

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 the

[issue1755179] Deadlocks with fork() and multithreading

Changes by Facundo Batista: -- assignee: -> facundobatista nosy: +facundobatista _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-lis