On Wed, Jan 8, 2014 at 10:19 AM, Doug Hellmann <[email protected]>wrote:
> > > > On Wed, Jan 8, 2014 at 9:34 AM, Sergey Skripnick > <[email protected]>wrote: > >> >> >> >>>> I'd like to explore whether the paramiko team will accept this code (or >>>> something like it). This seems like a perfect opportunity for us to >>>> contribute >>>> upstream. >>>> >>> >>> +1 >>> >>> The patch is not big and the code seems simple and reasonable enough >>> to live within paramiko. >>> >>> Cheers, >>> FF >>> >>> >>> >> I sent a pull request [0] but there is two things: >> >> nobody know when (and if) it will be merged >> it is still a bit low-level, unlike a patch in oslo >> > > Let's give the paramkio devs a little time to review it. > I had a brief conversation with Jeff Forcier, and he likes the idea of having some version of run() in paramiko. He will comment on the pull request with some details about what his plans were, but I think we can count on this going into a version of paramiko -- especially if we help. Doug > > >> >> About spur: spur is looks ok, but it a bit complicated inside (it uses >> separate threads for non-blocking stdin/stderr reading [1]) and I don't >> know how it would work with eventlet. >> > > That does sound like it might cause issues. What would we need to do to > test it? > > Doug > > > >> >> [0] https://github.com/paramiko/paramiko/pull/245 >> [1] https://github.com/mwilliamson/spur.py/blob/master/spur/io.py#L22 >> >> >> -- >> Regards, >> Sergey Skripnick >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
