This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ferringb
Recipients amaury.forgeotdarc, ferringb, gregory.p.smith, milko.krachounov, pitrou, zhigang
Date 2012-01-17.02:17:06
SpamBayes Score 9.79831e-06
Marked as misclassified No
Message-id <>
Just noticed this patch... aside from liking the intention, the api for this is going to grow tiresome quick since it expects the FDs to already be in place; is there any reasons a mapping wasn't used here, specifically of (src_fd|src_fileobj) -> target_fd ?

If that was fed in, post fork the client can shuffle around the fd's into appropriate positions- something the parent may not be able to do (threaded environment for example, or async in some respect).

I've had similar functionality in my own process code for a while, and have found it to be generally pretty easy to deal with- for subprocess it has the added benefit that the existing stdin/stdout/stderr bits could be pretty easily folded directly into it.

So... any reason this route wasn't considered, or just wasn't thought about?
Date User Action Args
2012-01-17 02:17:08ferringbsetrecipients: + ferringb, gregory.p.smith, amaury.forgeotdarc, pitrou, zhigang, milko.krachounov
2012-01-17 02:17:07ferringbsetmessageid: <>
2012-01-17 02:17:07ferringblinkissue6559 messages
2012-01-17 02:17:06ferringbcreate