FS#8760 - [python] subprocess.py weird behaviour

Attached to Project: Arch Linux
Opened by mangus (mangus) - Sunday, 25 November 2007, 21:55 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 23 February 2008, 20:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Developing a Pyqt4 application I came across a weird behaviour
of subprocess.py call as described here:
http://www.mail-archive.com/pyqt%40riverbankcomputing.com/msg10784.html
The patch in the thread (from ubuntu) seems solve my problem with my application.
patch for /usr/lib/python2.5 attached

Additional info:
* python-2.5.1-4


   patch (7.7 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 23 February 2008, 20:51 GMT
Reason for closing:  Won't implement
Additional comments about closing:  patch isn't gone upstream so far and one part doesn't apply well. patch it yourself if you really need it.
Comment by mangus (mangus) - Sunday, 25 November 2007, 23:21 GMT
can't find a way to edit the post, version of python affected is 2.5.1-3 actually in extra
Comment by mangus (mangus) - Sunday, 25 November 2007, 23:34 GMT
more info for the patch.
* Add debian/patches/subprocess-eintr-safety.dpatch:
- Create and use wrappers around read(), write(), and os.waitpid() in the
subprocess module which retry the operation on an EINTR (which happens
if e. g. an alarm was raised while the system call was in progress). It is
incredibly hard and inconvenient to sensibly handle this in
applications, so let's fix this at the right level.
- Patch based on original proposal of Peter Åstrand in
http://sourceforge.net/tracker/index.php?func=detail&aid=1068268&group_id=5470&atid=105470
- Add two test cases.
- (LP: #87292)

Loading...