Re: py-scipy and py-pandas with python[39-310]

[Paolo Vincenzo Olivo <vms%retrobsd.ddns.net@localhost>]

Sorry for not replying earlier; I somehow missed this message in the
multitude of mails hitting my inbox.
What follows is just for future reference. 

On 23/09/21 02:59PM, Greg Troxel wrote:
> Paolo Vincenzo Olivo <vins%NetBSD.org@localhost> writes:
> 
> > I see math/py[39-310]-pandas and math/py[39-310]-scipy failing on all
> > NetBSD bulk builds for pkgsrc-trunk.     
> 
> Does this mean that for 311 (default) it's ok?  To me that is the most
> important thing, but it of course should work elsewhere.

Yes, that was the case. Cython is python versioned while meson is not,
so si packages depending on cython packages as tool were failing due to
the fact that meson would always look for cython-3.11 regardless of the
python version in use.

> > Looking at the build log, it seems that meson fails to find
> > devel/py-cython even if it's pulled as TOOL dependency. Apparently meson
> > only looks for binaries named `cython' and `cython-3.11' (probably
> > reflecting PYTHON_VERSION_DEFAULT ?).    
> > devel/py-cython will install bin/cython-${PYVERSSUFFIX}, so the build
> > should be adjusted to look for the correct binary depending on the
> > python version in use.
> 
> It strikes me that meson should be told what the python version is and
> handle multiple versions, but perhaps the linux world does not allow
> multiple versions and thus people don't bother to make that work.   It
> sounds like you are suggesting that we patch in python-version-aware
> support and that makes sense to me.
> 

And this is indeed how @gutteridge managed to work around the problem,
at least for 2023Q3. See https://marc.info/?l=pkgsrc-changes&m=169558149012184