Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 02/14/2018 03:26 PM, Haïkel wrote: I agree it won't be simple, we will have to provide those repositories, determine how we will gate updates, fix puppet modules, POI, etc.. and that's only a beginning. That's why we won't be providing raw Fedora but rather a curated version and at some

Re: [openstack-dev] [tripleo][python3] python3 readiness?

2018-02-14 22:53 GMT+01:00 Tom Barron : > On 13/02/18 16:53 -0600, Ben Nemec wrote: >> >> >> >> On 02/13/2018 01:57 PM, Tom Barron wrote: >>> >>> Since python 2.7 will not be maintained past 2020 [1] it is a reasonable >>> conjecture that downstream distributions >>> will drop

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 13/02/18 16:53 -0600, Ben Nemec wrote: On 02/13/2018 01:57 PM, Tom Barron wrote: Since python 2.7 will not be maintained past 2020 [1] it is a reasonable conjecture that downstream distributions will drop support for python 2 between now and then, perhaps as early as next year. I'm not

Re: [openstack-dev] [tripleo][python3] python3 readiness?

2018-02-14 17:05 GMT+01:00 Ben Nemec : > > > On 02/13/2018 05:30 PM, David Moreau Simard wrote: >> >> On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec wrote: >>> >>> >>> I guess if RDO has chosen this path then we don't have much choice. >> >> >> This

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On Wed, Feb 14, 2018 at 11:19 AM, Ben Nemec wrote: > > I have to admit I don't entirely understand this constraint. CentOS 7 is in > support until 2024. I would think RHEL 7's timeline is similar or even > longer. If Python 2 is going out of support in 2020, does that

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 02/13/2018 10:24 PM, Haïkel wrote: RDO has *yet* to choose a plan, and people were invited to work on the "stabilized" repository draft [0]. If anyone has a better plan that fits all the constraints, please share it asap. Whatever the plan, we're launching it with the Rocky cycle. Among

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 02/13/2018 05:30 PM, David Moreau Simard wrote: On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec wrote: I guess if RDO has chosen this path then we don't have much choice. This makes it sound like we had a choice to begin with. We've already had a lot of discussions

Re: [openstack-dev] [tripleo][python3] python3 readiness?

2018-02-13 23:53 GMT+01:00 Ben Nemec : > > > On 02/13/2018 01:57 PM, Tom Barron wrote: >> >> Since python 2.7 will not be maintained past 2020 [1] it is a reasonable >> conjecture that downstream distributions >> will drop support for python 2 between now and then, perhaps

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec wrote: > > I guess if RDO has chosen this path then we don't have much choice. This makes it sound like we had a choice to begin with. We've already had a lot of discussions around the topic but we're ultimately stuck between a

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 02/13/2018 01:57 PM, Tom Barron wrote: Since python 2.7 will not be maintained past 2020 [1] it is a reasonable conjecture that downstream distributions will drop support for python 2 between now and then, perhaps as early as next year. I'm not sure I agree. I suspect python 2 support

[openstack-dev] [tripleo][python3] python3 readiness?

Since python 2.7 will not be maintained past 2020 [1] it is a reasonable conjecture that downstream distributions will drop support for python 2 between now and then, perhaps as early as next year. In Pike, OpenStack projects, including TripleO, added python 3 unit tests. That effort was a