Thanks for the well crafted explanation, and after talking to Paul I got a
clearer picture on which direction we should be heading and we should align
and work towards python3. Maybe I was not aware, my bad.
Sent: Wednesday, July 11, 2018 3:12 PM
To: Chan, Aaron Chun Yew <aaron.chun.yew.c...@intel.com>;
firstname.lastname@example.org; Burton, Ross <ross.bur...@intel.com>; Eggleton, Paul
Subject: Re: [PATCH] [yocto-autobuilder] init: Fix the import module yoctoabb &
On Wed, 2018-07-11 at 02:23 +0000, Chan, Aaron Chun Yew wrote:
> It appears that your using virtualenv (switch to python3) to startup
> your buildbot processes and not using the default python from host
> I am aware that you can switch interpreter to python2/3 in virtualenv.
> Shouldn’t we handle these for both in events users uses the default
> host distribution as default python2 and still make it worked? What is
> the best practices here and should all the buildbot- workers start in
> virtualenv defaults to python3 as well ? I am little lost right here,
> please advise.
There are multiple ways to achieve this, you can make /usr/bin/python point at
python3 too, or simply not install python2 on the controller.
Using virtualenv was just a simple way to illustrate how you can use it.
My worry about trying to support both python versions is that as you've found
out, there are problems that can occur in one that don't occur in the other,
which then means twice as much testing. Since python2 is an official "dead end"
and as a project we're trying hard to use python3 everywhere, it doesn't seem
to make sense to try and support python2 on new code such as the autobuilder?
yocto mailing list