openstack team mailing list archive

Thread
Date

Re: python 3 advocacy

To: Doug Hellmann <doug.hellmann@xxxxxxxxxxxxx>, Thierry Carrez <thierry@xxxxxxxxxxxxx>
From: "Haynes, Dave (Cloud Services)" <dave.haynes@xxxxxx>
Date: Tue, 31 Jul 2012 09:37:21 +0000
Accept-language: en-GB, en-US
Cc: "openstack-dev@xxxxxxxxxxxxxxxxxxx" <openstack-dev@xxxxxxxxxxxxxxxxxxx>, "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <CADb+p3QwkHnsLhSO9V-XC3Y7cwC36RzgkCGj0SozX4iFODgySg@mail.gmail.com>
Thread-index: AQHNbwAVFqPis0L4c06gcwAxkI3nPw==
Thread-topic: [Openstack] python 3 advocacy

> I would not assume that *-paste.ini files always need to be there...
> Paste is a pain point if we are to support Python 3 one day, so it's
> also on the black list of the (still inexistant) OpenStack Python3
> advocacy group.

> Who else is interested in contributing to Python 3 support in a future version of OpenStack?

Please add me to your list. I see migration to Python 3 as bringing benefits in itself, and also as a driver to the refactoring and componentization of the Openstack product.


> We exist, we're just not organized, yet. :-)

Perhaps _organization_ isn't what's needed ;-)

Dave Haynes

References

python 3 advocacy (was Re: Hiding complexity of paste config files from operators)
From: Doug Hellmann, 2012-07-30