[Bug 1077153] Re: _DummyThread' object has no attribute '_Thread__block

[Dmitrijs Ledkovs]

** Summary changed:

- Backport request: http://bugs.python.org/issue14308
+ _DummyThread' object has no attribute '_Thread__block

** Changed in: python2.7 (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: python2.7 (Ubuntu Precise)
    Milestone: None => ubuntu-12.04.3

** Description changed:

- Resolved Upstream Issue: http://bugs.python.org/issue14308
+ [Impact]
  
- Based on my experimentation with the test script included in that ticket
- the threads throw the exceptions when the context switch back to the
- thread happens, not on cleanup of the thread (throw a print and
- sys.stdout.flush() on either side of the sleep to demonstrate this),
- which means this could have a drastic effect on programs which use both
- threads and os.fork() (through, say, subprocess.Popen).
+ Based on the test script available at the upstream issue link, the
+ exception is thrown in programs that use threads and os.fork() (like
+ could be the case with subprocess).
+ 
+ As reported upstream, the exception when a "dummy" thread is in the
+ threading module's active list after a fork().
+ 
+ [Test Case]
+ 
+ Run the following program, available in the upstream issue:
+ 
+ http://bugs.python.org/file25511/bad-thread.py
+ 
+ to reproduce the problem.
+ 
+ [Regression Potential]
+ 
+ None seen at the moment.
+ Upstream patch contains also a test case to address this issue:
+ 
+ http://hg.python.org/cpython/rev/ab9d6c4907e7

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1077153

Title:
  _DummyThread' object has no attribute '_Thread__block

Status in Python:
  Fix Released
Status in “python2.7” package in Ubuntu:
  Fix Released
Status in “python2.7” source package in Precise:
  Triaged

Bug description:
  [Impact]

  Based on the test script available at the upstream issue link, the
  exception is thrown in programs that use threads and os.fork() (like
  could be the case with subprocess).

  As reported upstream, the exception when a "dummy" thread is in the
  threading module's active list after a fork().

  [Test Case]

  Run the following program, available in the upstream issue:

  http://bugs.python.org/file25511/bad-thread.py

  to reproduce the problem.

  [Regression Potential]

  None seen at the moment.
  Upstream patch contains also a test case to address this issue:

  http://hg.python.org/cpython/rev/ab9d6c4907e7

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1077153/+subscriptions