[CRIU] CRIU and Python 3

[Adrian Reber]

On Sat, Apr 21, 2018 at 11:30:59AM -0700, Andrei Vagin wrote:
> On Fri, Apr 20, 2018 at 04:25:08PM +0200, Adrian Reber wrote:
> > Python 2.7 will be retired 2020 (https://pythonclock.org/) and as
> > Fedora might drop Python 2.7 at some point and as RHEL 7.5 says:
> > 
> >  Python 2 will be replaced with Python 3 in the next Red Hat Enterprise
> >  Linux (RHEL) major release. 
> > 
> >  https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/7.5_release_notes/#chap-Red_Hat_Enterprise_Linux-7.5_Release_Notes-Deprecated_Functionality
> > 
> > 
> > Has there been any discussion about using Python 3 in CRIU? I am
> > currently trying to port a few CRIU things to Python 3 (not zdtm yet)
> > but wanted to check if somebody did already the work?
> > 
> > For me as a packager it would be nice if we could support Python 2.7 and
> > Python 3 and I guess it should be possible at least with CRIU and CRIT.
> > Not sure about zdtm and not really necessary as zdtm is not shipped as
> > a package for the end user. But it would be nice if the things installed
> > on an end user system via a package would support both Python versions
> > for some time.
> 
> I ported zdtm.py on python3 a few month ago
> https://github.com/avagin/criu/commits/python3
> 
> The problem here is that we can't use one code for python2 and python3,
> and I don't want to maintain two versions. If we are going to switch to
> python3, we probably have to stop supporting python2. It is only about
> zdtm.py.

A python3 only zdtm.py sounds good to me. I think crit can be changed to
support Python 2.7 and Python 3. I will finish those patches and send
them to the list for further discussion.

		Adrian