On Fri, Sep 11, 2009 at 08:06, Cameron Simpson cs@zip.com.au wrote:
On 25Jul2009 10:25, Gregory P. Smith greg@krypto.org wrote: | On Thu, Jul 23, 2009 at 4:28 PM, Thomas Woutersthomas@python.org wrote: | > So attached (and at http://codereview.appspot.com/96125/show ) is a | > preliminary fix, correcting the problem with os.fork(), os.forkpty() and | > os.fork1(). This doesn't expose a general API for C code to use, for two | > reasons: it's not easy, and I need this fix more than I need the API change | > :-) (I actually need this fix myself for Python 2.4, but it applies fairly | > cleanly.) | | This looks good to me. [...]
Where's this stand with respect to the upcoming Python 2.6.3?
Unless anyone speaks up, I'll submit the fix (without the change in semantics on AIX) to release26-maint early next week, so it would be in 2.6.3.