[OE-core] [PATCH] python: make python2 and python3 alternatives to python

Burton, Ross ross.burton at intel.com
Tue Apr 18 09:33:16 UTC 2017


On 18 April 2017 at 09:44, Dmitry Rozhkov <dmitry.rozhkov at linux.intel.com>
wrote:

> I've just checked PEP-349. It recommends that
>
> "- The more general python command should be installed whenever any
> version of Python 2 is installed and should invoke the same version of
> Python as the python2 command (however, note that some distributions
> have already chosen to have python implement the python3 command; see
> the Rationale and Migration Notes below)."
>
> The proposed patch doesn't violate this recommendation, because
> "whenever" Python 2 is installed the python command still invokes
> python2.
>

Only out of the box: you can install py2 and py3 and set the alternatives
so that python is python3.

If I understood correctly OE-core is not a distribution, but a tool to
> create "a custom one". I would rather allow people to create
> distributions where python3 is the default like in Arch Linux.


Personally I feel the PEP is an attempt to limit the damage caused by Arch
ignoring the Python maintainers, and I'd prefer not to spread the
impression that 'python' could be Python 3.  Unless you code incredibly
carefully it's not simple to have a script that doesn't care if it runs
under Py2 or Py3.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170418/31d4aa42/attachment-0002.html>


More information about the Openembedded-core mailing list