[OE-core] [PATCH] python-numpy: Avoid installing copy of f2py script

[Richard Purdie]

On Mon, 2019-05-20 at 07:52 -0700, Khem Raj wrote:
> On Sun, May 19, 2019 at 11:56 PM Alejandro Enedino Hernandez
> Samaniego <alejandro.enedino.hernandez-samaniego at xilinx.com> wrote:
> > Hey Khem,
> > 
> > 
> > On 5/18/19 10:09 PM, Khem Raj wrote:
> > >
> > >
> > > On 5/17/19 4:49 PM, Alejandro Enedino Hernandez Samaniego wrote:
> > >> Both python-numpy and python3-numpy try to install the file:
> > >>
> > >> ${D}/${bindir}/f2py
> > >>
> > >> which causes an error during do_rootfs since the package
> > manager 
> > >> complains about that.
> > >>
> > >> The numpy packages create basically copies of f2py script with
> > the 
> > >> following names:
> > >> f2py (on both)
> > >> f2py2 (on python 2)
> > >> f2py2.7 (on python 2)
> > >> f2py3 (on python 3)
> > >> f2py3.7 (on python 3)
> > >>
> > >> Remove the copy of f2py from python-numpy in favor of using the
> > one 
> > >> from python3
> > >> to avoid installation issues at do_rootfs().
> > >>
> > >
> > > what if one does not install py3 ?
> > 
> > 
> > If you only install py2, you could still execute f2py2 or f2py2.7,
> > I'm 
> > simply
> > 
> > favoring the py3 installation by default but it should be mostly
> > harmless
> > 
> > since there's still two other copies of the script with different
> > names.
> 
> I think it should be such that it’s used from py2 if py3 is not
> installed since otherwise it might break scripts 

Given we're strongly favouring py3 now, I'd hope there aren't many such
users and if there are, this might encourage them to move to py3? I'm
not too worried about the lack of a py2 case for this as do we really
want to add the complexity?

If there are a load of py2 users and this will break things for them,
fine but are there such users?

Cheers,

Richard