On 18 April 2017 at 09:44, Dmitry Rozhkov
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
On Thu, 2017-04-13 at 15:47 +0100, Burton, Ross wrote:
>
> On 13 April 2017 at 11:15, Alexander Kanavin .intel.com> wrote:
> > This runs against upstream recommendation and common distro
> > practice. And it will break scripts that have not been ported to
> > Python 3.
On 13 April 2017 at 11:15, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> This runs against upstream recommendation and common distro practice. And
> it will break scripts that have not been ported to Python 3. Please fix the
> scripts instead to refer to python 3 whenever
On 04/13/2017 01:15 PM, Alexander Kanavin wrote:
On 04/13/2017 11:33 AM, Dmitry Rozhkov wrote:
If only python3 is installed on an image nothing provides
/usr/bin/python even though many scripts compatible with
both python2 and python3 just state `#!/usr/bin/env python`
in their shebang line.
On 04/13/2017 11:33 AM, Dmitry Rozhkov wrote:
If only python3 is installed on an image nothing provides
/usr/bin/python even though many scripts compatible with
both python2 and python3 just state `#!/usr/bin/env python`
in their shebang line.
Make python and python3 recipes provide
If only python3 is installed on an image nothing provides
/usr/bin/python even though many scripts compatible with
both python2 and python3 just state `#!/usr/bin/env python`
in their shebang line.
Make python and python3 recipes provide alternatives for
/usr/bin/python and