On 05/26/2015 10:31 AM, Russell Bryant wrote: > On 05/21/2015 10:23 PM, Andy Hill wrote: >>> As a consequence, this requires dropping support for old versions of >>> XenServer. I don't expect that to be much of a problem. >> >> Unfortunately, the most recent release of XenServer (6.5) still ships >> with Python 2.4. >> >>> +Open vSwitch requires a version of XenServer (XCP) that includes a >>> +modern version of Python (2.7 or later). This excludes older releases >>> +based on Centos, which have Python 2.4. >> >> XCP seems looks EOL on after XenServer was open sourced.[1] >> >> Can we defer this until a later Open vSwitch release? Maybe the next LTS? >> >> [1] >> http://www.xenproject.org/component/content/article/100-misc/148-xcp-and-xenserver-faq.html >> - See "I am a user of XCP: how am I impacted?" > > This is going to get more and more painful. We may just have to fork > this library for OpenStack for now so we can carry a patch set to > support Python 3. It's a last resort, but we can't really wait if we > want to use this in OpenStack. >
I should clarify a bit ... if I did this, it would be with the full intention to get all the patches submitted/merged once we're ready to increase the minimum Python version. One option would be to create a python3 branch in the ovs repo with the intention to merge it into master after the 2.4 release. Another option would be to take the opportunity to split out the Python library into its own git repo. The new git repo would have this patch series and Python 3 support for now and more Python 3 fixes over time. After ovs 2.4, releases of the Python lib could start coming from the new repo. I don't have a strong preference. I just want to help find a way that we can move forward with Python 3 support so that this code remains compatible with its use in OpenStack. -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
