<div dir="ltr">I'd rather go with Heat approach (job first) because it makes easier to track what is left to port to Py34 and track progress in this area<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Times New Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="font-family:arial;font-size:small">Sincerely yours,<br>Stan Lagun<br>Principal Software Engineer @ Mirantis</span></span><br><span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Times New Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="font-family:arial;font-size:small"><br><a href="mailto:slagun@mirantis.com" target="_blank"></a></span></span></div></div></div>
<br><div class="gmail_quote">On Mon, Jun 8, 2015 at 2:46 PM, Kirill Zaitsev <span dir="ltr"><<a href="mailto:kzaitsev@mirantis.com" target="_blank">kzaitsev@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I’ve looked into several OS projects, and they first seen to implement py3 support and create a job later. (Except for heat. They already have a non-voting py34, which seem to fail every time =))</div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I suggest we do the same: first make murano work on py34, then make a py34 job. I’ll file a blueprint shortly.</div><span class=""> <br> <div><div style="font-family:helvetica,arial;font-size:13px">-- <br>Kirill Zaitsev<br>Murano team</div><div style="font-family:helvetica,arial;font-size:13px">Software Engineer</div><div style="font-family:helvetica,arial;font-size:13px">Mirantis, Inc</div></div> <br></span><div><div class="h5"><p style="color:#000">On 2 Jun 2015 at 15:58:17, Serg Melikyan (<a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a>) wrote:</p> <blockquote type="cite"><span><div><div></div><div>Hi Kirill,<br><br>I agree with Alexander that we should not remove support for python<br>2.6 in python-muranoclient.<br><br>Regarding adding python-3 jobs - great idea! But we need to migrate<br>python-muranoclient to yaql 1.0 first and then add python-3 jobs,<br>because previous versions of yaql are not compatible with python-3.<br><br>On Tue, Jun 2, 2015 at 3:33 PM, Alexander Tivelkov<br><<a href="mailto:ativelkov@mirantis.com" target="_blank">ativelkov@mirantis.com</a>> wrote:<br>> Hi Kirill,<br>><br>> Client libraries usually have wider range of python requirements, as they<br>> may be run on various kinds of legacy environments, including the ones with<br>> python 2.6. only.<br>> Murano is definitely not the only project in Openstack which still maintains<br>> py26 compatibility for its client: nova, glance, cinder and other integrated<br>> ones do this.<br>><br>> So, I would not drop py26 support for client code without any good reasons<br>> to. Are there any significant reasons to do it?<br>> Regarding py3.4 - this is definitely a good idea.<br>><br>><br>> --<br>> Regards,<br>> Alexander Tivelkov<br>><br>> On Tue, Jun 2, 2015 at 3:04 PM, Kirill Zaitsev <<a href="mailto:kzaitsev@mirantis.com" target="_blank">kzaitsev@mirantis.com</a>><br>> wrote:<br>>><br>>> It seems that python-muranoclient is the last project from murano-official<br>>> group, that still supports python2.6. Other projects do not have a 2.6<br>>> testing job (correct me if I’m wrong).<br>>><br>>> Personally I think it’s time to drop support for 2.6 completely, and add<br>>> (at least non-voting) jobs with python3.4 support tests.<br>>> It seems to fit the whole process of moving OS projects towards python 3:<br>>> <a href="https://etherpad.openstack.org/p/liberty-cross-project-python3" target="_blank">https://etherpad.openstack.org/p/liberty-cross-project-python3</a><br>>><br>>> What do you think? Does anyone have any objections?<br>>><br>>> --<br>>> Kirill Zaitsev<br>>> Murano team<br>>> Software Engineer<br>>> Mirantis, Inc<br>>><br>>> __________________________________________________________________________<br>>> OpenStack Development Mailing List (not for usage questions)<br>>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>>><br>><br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>><br><br><br><br>-- <br>Serg Melikyan, Senior Software Engineer at Mirantis, Inc.<br><a href="http://mirantis.com" target="_blank">http://mirantis.com</a> | <a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></div></div></span></blockquote></div></div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>