Open Stack

On Wed, 2013-06-05 at 13:33 -0400, Doug Hellmann wrote:
> Do we have an eventlet expert available to figure out if this is going to
> bite us?
> 
> Doug
> 
> ---------- Forwarded message ----------
> From: Sergey Shepelev <temotor at gmail.com>
> Date: Tue, Jun 4, 2013 at 1:26 PM
> Subject: Eventlet 0.13 is going to have minor incompatible change in
> subprocess API
> To: comp-lang-python-announce at moderators.isc.org
> 
...
> If you are curious what's going on, here's the full story:
> Python 3.3 introduced `timeout` kwarg to lots of methods of subprocess
> module. The RHEL guys backported it to their Python 2.6 package. At some
> point, the code they used started to use subprocess from Eventlet which
> does not have the `timeout` kwarg.
> https://bitbucket.org/eventlet/eventlet/issue/89
> https://bitbucket.org/eventlet/eventlet/pull-request/30
> Now in Eventlet, I am going to introduce the `timeout` argument and to make
> it forward compatible with Python3, it's going to get first place, like in
> stdlib.
> To interested people, you may leave a comment in this discussion or in this
> Github thread: https://github.com/eventlet/eventlet/pull/34

This is actually really good news. We'll be able to remove
contrib/redhat-eventlet.patch from all projects when it's released.

Cheers,
Mark.