[openstack-dev] [Nova] blueprint: Nova with py33 compatibility
We will move to Python33 in the future. More and more OpenStack projects including python-novaclient are Python33 compatible. Do we have plan to make Nova python33 compatible ? As I know, oslo.messaging will not support python33 in Icehouse,this is just one dependency for Nova, that means we can't finish it in Icehouse for Nova. I registered one blueprint [1]to make us move to Python33 smoothly in the future. Python33 compatibility would be taken into account while reviewing code. We have to add py33 check/gate jobs to check Py33 compatibility. This blueprint could be marked as implemented only until Nova code can pass these jobs. [1] https://blueprints.launchpad.net/nova/+spec/nova-py3kcompat -- ChangBo Guo(gcb) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] blueprint: Nova with py33 compatibility
Yes, a Jenkins job is not useful currently. I would like to submit some commits to fix known python 3 support issues as we did in oslo-incubator. Another question is how to make new changes avoid regression, Maybe we need add more rules about this in hacking and consider python 3 support in review process. 2014-02-21 5:10 GMT+08:00 Russell Bryant rbry...@redhat.com: On 02/20/2014 09:43 AM, 郭小熙 wrote: We will move to Python33 in the future. More and more OpenStack projects including python-novaclient are Python33 compatible. Do we have plan to make Nova python33 compatible ? As I know, oslo.messaging will not support python33 in Icehouse,this is just one dependency for Nova, that means we can't finish it in Icehouse for Nova. I registered one blueprint [1]to make us move to Python33 smoothly in the future. Python33 compatibility would be taken into account while reviewing code. We have to add py33 check/gate jobs to check Py33 compatibility. This blueprint could be marked as implemented only until Nova code can pass these jobs. [1] https://blueprints.launchpad.net/nova/+spec/nova-py3kcompat Python 3 support is certainly a goal that *all* OpenStack projects should be aiming for. However, for Nova, I don't think Nova's code is actually our biggest hurdle. The hardest parts are dependencies that we have that don't support Python 3. A big example is eventlet. We're so far off that I don't even think a CI job is useful yet. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ChangBo Guo(gcb) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] blueprint: Nova with py33 compatibility
On Thu, Feb 20, 2014 at 3:48 PM, 郭小熙 glongw...@gmail.com wrote: Yes, a Jenkins job is not useful currently. I would like to submit some commits to fix known python 3 support issues as we did in oslo-incubator. Another question is how to make new changes avoid regression, Maybe we need add more rules about this in hacking and consider python 3 support in review process. What is the benefit in doing this? Until we have a roadmap to get the dependencies working this seems premature. 2014-02-21 5:10 GMT+08:00 Russell Bryant rbry...@redhat.com: On 02/20/2014 09:43 AM, 郭小熙 wrote: We will move to Python33 in the future. More and more OpenStack projects including python-novaclient are Python33 compatible. Do we have plan to make Nova python33 compatible ? As I know, oslo.messaging will not support python33 in Icehouse,this is just one dependency for Nova, that means we can't finish it in Icehouse for Nova. I registered one blueprint [1]to make us move to Python33 smoothly in the future. Python33 compatibility would be taken into account while reviewing code. We have to add py33 check/gate jobs to check Py33 compatibility. This blueprint could be marked as implemented only until Nova code can pass these jobs. [1] https://blueprints.launchpad.net/nova/+spec/nova-py3kcompat Python 3 support is certainly a goal that *all* OpenStack projects should be aiming for. However, for Nova, I don't think Nova's code is actually our biggest hurdle. The hardest parts are dependencies that we have that don't support Python 3. A big example is eventlet. We're so far off that I don't even think a CI job is useful yet. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ChangBo Guo(gcb) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] blueprint: Nova with py33 compatibility
On 02/20/2014 07:34 PM, Joe Gordon wrote: On Thu, Feb 20, 2014 at 3:48 PM, 郭小熙 glongw...@gmail.com wrote: Yes, a Jenkins job is not useful currently. I would like to submit some commits to fix known python 3 support issues as we did in oslo-incubator. Another question is how to make new changes avoid regression, Maybe we need add more rules about this in hacking and consider python 3 support in review process. What is the benefit in doing this? Until we have a roadmap to get the dependencies working this seems premature. +1 -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] blueprint: Nova with py33 compatibility
agree with that , thank you the the input , let hold on this until we have a clear roadmap. 2014-02-21 8:47 GMT+08:00 Sean Dague s...@dague.net: On 02/20/2014 07:34 PM, Joe Gordon wrote: On Thu, Feb 20, 2014 at 3:48 PM, 郭小熙 glongw...@gmail.com wrote: Yes, a Jenkins job is not useful currently. I would like to submit some commits to fix known python 3 support issues as we did in oslo-incubator. Another question is how to make new changes avoid regression, Maybe we need add more rules about this in hacking and consider python 3 support in review process. What is the benefit in doing this? Until we have a roadmap to get the dependencies working this seems premature. +1 -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ChangBo Guo(gcb) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
