On Sun, 26 Aug 2018 at 23:48, Dmitry Shachnev <email@example.com> wrote:
On Sun, Aug 26, 2018 at 10:01:38PM +1200, Michael Hudson-Doyle wrote:
> So the problem is that python3-numpy contains a version of 'f2py' for each
> supported version of Python. I guess the proper fix involves creating a
> separate package for the each version of f2py? python3.6-f2py,
> python3.7-f2py, and have python3-numpy depend on the one for the default
> version of Python?
This will mean having a new package name whenever we add a new supported
Python version. It will be very inconvenient to maintain.
Better remove the versioned scripts altogether and use "python3.x -m
numpy.f2py" when one really needs a non-default Python version.
Yes, that's probably a better plan.