[Bug 1100343] Re: Error on some forked thread termination in python threading module

[Chris Halse Rogers]

Hello Charles, or anyone else affected,

Accepted python2.7 into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/python2.7/2.7.3-0ubuntu3.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: python2.7 (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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/1100343

Title:
  Error on some forked thread termination in python threading module

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

Bug description:
  I'd like for the fix to python issue 14308 to be ported to python2.7 in Ubuntu Precise.
  http://bugs.python.org/issue14308

  As near as I can tell, it affects python 2.7 threading.Thread threads
  which have were are created, call currentThread(), are then forked,
  and then terminate.

  For my purposes, it is affecting some code I wrote which does spawns
  processes to run simple shell scripts in the background.  It also
  seems to have affected various Django projects as well as Duplicity as
  per https://bugs.launchpad.net/duplicity/+bug/946993.  As I read that
  ticket, it was fixed via a workaround in Duplicity/Debbugs?  It seems
  to me that this is really a Python2.7 bug.

  I was able to easily reproduce this bug with this small test case as per the python bug ticket on Ubuntu Precise Server:
  <code>
  #!/usr/bin/python
  import os
  import thread
  import threading
  import time

  def t():
      threading.currentThread() # Populate threading._active with a DummyThread
      time.sleep(3)

  thread.start_new_thread(t, ())
  time.sleep(1)

  pid = os.fork()
  if pid == 0:
      os._exit(0)

  os.waitpid(pid, 0)
  </code>

  The fix is a simple two-line patch to threading.py implemented by the
  fix for python bug 14308.  I have also attached that, again from
  http://bugs.python.org/issue14308.

  As far as I can tell, this has not made its way from upstream to
  Precise.  My sincerest apologies if this is reported elsewhere or my
  report is somehow inappropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1100343/+subscriptions