Bug 814492

Summary: python package need to be updated to eliminate Pipe and Thread bugs
Product: [Fedora] Fedora Reporter: wenchao xia <xiawenc>
Component: pythonAssignee: Dave Malcolm <dmalcolm>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: danken, dmalcolm, ivazqueznet, jonathansteffan, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 02:52:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 808853    
Attachments:
Description Flags
Test program to produce the python subprocess and thread bug none

Description wenchao xia 2012-04-20 01:59:00 UTC
Created attachment 578830 [details]
Test program to produce the python subprocess and thread bug

Description of problem:
    python with a version lower than v2.7.3 and v3.2, have bad bugs in Pipe and Thread, it is a race condition.

Version-Release number of selected component (if applicable):
v2.7.2

How reproducible:
    often but not every time.


Steps to Reproduce:
1. download the attachment as a test script.
2. run it for several times.
3. observe that if thread 1 hangs.
  
Actual results:
   sometimes it hangs.

Expected results:
   it should never hang.

Additional info:
    Python 2.7.3 was just released on 11 April 2012, and my test script passed on it. When I spy on the source code of cpython project, I found no special patch fixing the bug, and the information I got is that many subprocess changes was back ported from python3.2+, and the mechanisms changes. Related python issue track:
    http://bugs.python.org/issue2320
    I tested my script on some version of Python: result is:
    Python3: later than Python v3.2.2, pass.
    Python2: Python v2.7.3, pass. Python v2.7.2, fail. Python v2.7.2+(ubuntu), fail.

Comment 2 wenchao xia 2012-04-23 03:15:26 UTC
Downloaded and tried, so far it is good, and wait for a update package available in yum.

Comment 3 Thomas Spura 2012-04-23 08:10:28 UTC
(In reply to comment #2)
> Downloaded and tried, so far it is good, and wait for a update package
> available in yum.

It is available in updates-testing:
e.g. as root:
"yum --enablerepo=updates-testing update python"

Comment 4 Fedora End Of Life 2013-01-17 01:42:54 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-14 02:52:15 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.