[ClusterLabs] Proposed change for 1.1.16: ending python 2.6 compatibility

2016-07-05 Thread Ken Gaillot
As you may be aware, python 3 is a significant, backward-compatible restructuring of the python language. Most development of the python 2 series has ended, and support for python 2 will completely end in 2020. Pacemaker currently uses python only in its test suites. At some point, we may convert

Re: [ClusterLabs] Proposed change for 1.1.16: ending python 2.6 compatibility

2016-07-05 Thread Digimer
On 05/07/16 01:31 PM, Ken Gaillot wrote: > As you may be aware, python 3 is a significant, backward-compatible > restructuring of the python language. Most development of the python 2 > series has ended, and support for python 2 will completely end in 2020. > > Pacemaker currently uses python only

Re: [ClusterLabs] Proposed change for 1.1.16: ending python 2.6 compatibility

2016-07-06 Thread Ken Gaillot
On 07/05/2016 06:49 PM, Digimer wrote: > On 05/07/16 01:31 PM, Ken Gaillot wrote: >> As you may be aware, python 3 is a significant, backward-compatible >> restructuring of the python language. Most development of the python 2 >> series has ended, and support for python 2 will completely end in 202

Re: [ClusterLabs] Proposed change for 1.1.16: ending python 2.6 compatibility

2016-07-11 Thread Kristoffer Grönlund
Ken Gaillot writes: > So, I propose that Pacemaker stop supporting python 2.6 as of the next > version (1.1.16, expected sometime in the fall or winter). Not all our > python code is likely to be python3-compatible by that time, but we can > start moving in that direction. > > If anyone has any r