[openstack-dev] Swift, netifaces, PyPy, and cffi
Vishvananda Ishaya
vishvananda at gmail.com
Thu Aug 15 00:17:24 UTC 2013
On Aug 14, 2013, at 11:12 AM, Jarret Raim <jarret.raim at RACKSPACE.COM> wrote:
> I vote for including cffi. We are going to use a cffi lib as part of Barbican (key management) anyway, so I'd like to see wider acceptance.
>
> Jarret
+1
cffi rocks
Vish
>
> From: Alex Gaynor <alex.gaynor at gmail.com>
> Reply-To: OpenStack List <openstack-dev at lists.openstack.org>
> Date: Wednesday, August 14, 2013 12:12 PM
> To: "openstack at nemebean.com" <openstack at nemebean.com>, OpenStack List <openstack-dev at lists.openstack.org>
> Subject: Re: [openstack-dev] Swift, netifaces, PyPy, and cffi
>
> I just chatted with the Python product owner at Red Hat, he says this is going to make it's way to the next step later today (this past weekend was a Fedora conference), so this should be happening soon.
>
> Joe: Yup, I'm familiar with that piece (I had lunch with Vish the other week and he's the one who suggested Swift as the best place to get started with OpenStack + PyPy). For those who don't know I'm one of the core developers of PyPy :)
>
> Alex
>
>
>
> On Wed, Aug 14, 2013 at 9:24 AM, Ben Nemec <openstack at nemebean.com> wrote:
>> On 2013-08-13 16:58, Alex Gaynor wrote:
>>> One of the issues that came up in this review however, is that cffi is
>>> not packaged in the most recent Ubuntu LTS (and likely other
>>> distributions), although it is available in raring, and in a PPA
>>> (http://packages.ubuntu.com/raring/python-cffi [2]
>>> nd https://launchpad.net/~pypy/+archive/ppa?field.series_filter=precise
>>> [3] respectively).
>>>
>>>
>>> As a result of this, we wanted to get some feedback on which direction
>>> is best to go:
>>>
>>> a) cffi-only approach, this is obviously the simplest approach, and
>>> works everywhere (assuming you can install a PPA, use pip, or similar
>>> for cffi)
>>> b) wait until the next LTS to move to this approach (requires waiting
>>> until 2014 for PyPy support)
>>> c) Support using either netifaces or cffi: most complex, and most
>>> code, plus "one or the other" dependencies aren't well supported by
>>> most tools as far as I know.
>>
>> It doesn't appear to me that this is available for RHEL yet, although it looks like they're working on it: https://admin.fedoraproject.org/updates/python-cffi-0.6-4.el6
>>
>> That's also going to need to happen before we can do this, I think.
>>
>> -Ben
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
> "The people's good is the highest law." -- Cicero
> GPG Key fingerprint: 125F 5C67 DFE9 4084
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/00f1b139/attachment.html>
More information about the OpenStack-dev
mailing list