[openstack-dev] [Oslo] Layering olso.messaging usage of config
Flavio Percoco
flavio at redhat.com
Wed Dec 4 09:52:17 UTC 2013
On 04/12/13 10:14 +0100, Julien Danjou wrote:
>On Tue, Dec 03 2013, Joshua Harlow wrote:
>
>> Another question that¹s come up recently. Python 3.3 support? Will
>> oslo.messaging achieve that? Maybe its a later goal, but it seems like one
>> that is required (and should almost be expected of new libraries imho).
>> Thoughts? Seems to be mainly eventlet that is the blocker for
>> oslo.messaging (so maybe it can be adjusted to work with things other than
>> eventlet to make it python33 compat).
>
>I didn't dig into that yet, but I think the only blocker shall be
>eventlet indeed.
>
>However, the eventlet usage in oslo.messaging is smartly decoupled from
>the rest of the code. It's only used in an executor. That means only
>this executor module won't be available on Python 3. But there's still
>the generic one, and any other somebody would add.
Correct. The idea there is be able to support different executors that
will make it easier to port oslo.messaging to Py3K without depending
on the support of it for eventlet / gevent.
I just created this:
https://blueprints.launchpad.net/oslo.messaging/+spec/asyncio-executor
FF
--
@flaper87
Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131204/e0354eb5/attachment.pgp>
More information about the OpenStack-dev
mailing list