Stan, +100500 On Fri, Jun 12, 2015 at 3:13 PM, Stan Lagun <[email protected]> wrote: > > 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 > > Sincerely yours, > Stan Lagun > Principal Software Engineer @ Mirantis > > > On Mon, Jun 8, 2015 at 2:46 PM, Kirill Zaitsev <[email protected]> wrote: >> >> 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 =)) >> >> I suggest we do the same: first make murano work on py34, then make a py34 >> job. I’ll file a blueprint shortly. >> >> -- >> Kirill Zaitsev >> Murano team >> Software Engineer >> Mirantis, Inc >> >> On 2 Jun 2015 at 15:58:17, Serg Melikyan ([email protected]) wrote: >> >> Hi Kirill, >> >> I agree with Alexander that we should not remove support for python >> 2.6 in python-muranoclient. >> >> Regarding adding python-3 jobs - great idea! But we need to migrate >> python-muranoclient to yaql 1.0 first and then add python-3 jobs, >> because previous versions of yaql are not compatible with python-3. >> >> On Tue, Jun 2, 2015 at 3:33 PM, Alexander Tivelkov >> <[email protected]> wrote: >> > Hi Kirill, >> > >> > Client libraries usually have wider range of python requirements, as they >> > may be run on various kinds of legacy environments, including the ones with >> > python 2.6. only. >> > Murano is definitely not the only project in Openstack which still >> > maintains >> > py26 compatibility for its client: nova, glance, cinder and other >> > integrated >> > ones do this. >> > >> > So, I would not drop py26 support for client code without any good reasons >> > to. Are there any significant reasons to do it? >> > Regarding py3.4 - this is definitely a good idea. >> > >> > >> > -- >> > Regards, >> > Alexander Tivelkov >> > >> > On Tue, Jun 2, 2015 at 3:04 PM, Kirill Zaitsev <[email protected]> >> > wrote: >> >> >> >> It seems that python-muranoclient is the last project from murano-official >> >> group, that still supports python2.6. Other projects do not have a 2.6 >> >> testing job (correct me if I’m wrong). >> >> >> >> Personally I think it’s time to drop support for 2.6 completely, and add >> >> (at least non-voting) jobs with python3.4 support tests. >> >> It seems to fit the whole process of moving OS projects towards python 3: >> >> https://etherpad.openstack.org/p/liberty-cross-project-python3 >> >> >> >> What do you think? Does anyone have any objections? >> >> >> >> -- >> >> Kirill Zaitsev >> >> Murano team >> >> Software Engineer >> >> Mirantis, Inc >> >> >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> >> Unsubscribe: [email protected]?subject:unsubscribe >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> > >> > >> > __________________________________________________________________________ >> > OpenStack Development Mailing List (not for usage questions) >> > Unsubscribe: [email protected]?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> >> >> >> -- >> Serg Melikyan, Senior Software Engineer at Mirantis, Inc. >> http://mirantis.com | [email protected] >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >
-- Serg Melikyan, Senior Software Engineer at Mirantis, Inc. http://mirantis.com | [email protected] __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
