Re: problems with wip/py-pyside-setup

[mlh%goathill.org@localhost (MLH)]

MLH wrote:
> MLH wrote:
> > 
> > I think what is happening is that py-pyside-setup is not correctly
> > setting up the numpy includes as it should with lib/_utils_impl.py :
> > 
> > @set_module('numpy')
> > def get_include():
> >     """
> >     Return the directory that contains the NumPy \\*.h header files.
> > 
> >     Extension modules that need to compile against NumPy may need to use this
> >     function to locate the appropriate include directory.
> > 
> >     Notes
> >     -----
> >     When using ``setuptools``, for example in ``setup.py``::
> > 
> >         import numpy as np
> >         ...
> >         Extension('extension_name', ...
> >                   include_dirs=[np.get_include()])
> >         ...
> > 
> >     Note that a CLI tool ``numpy-config`` was introduced in NumPy 2.0, using
> >     that is likely preferred for build systems other than ``setuptools``::
> > 
> >         $ numpy-config --cflags
> >         -I/path/to/site-packages/numpy/_core/include
> > 
> >         # Or rely on pkg-config:
> >         $ export PKG_CONFIG_PATH=$(numpy-config --pkgconfigdir)
> >         $ pkg-config --cflags
> >         -I/path/to/site-packages/numpy/_core/include
> > 
> >     Examples
> >     --------
> >     >>> np.get_include()
> >     '.../site-packages/numpy/core/include'  # may vary
> > 
> >     """
> >     import numpy
> >     if numpy.show_config is None:
> >         # running from numpy source directory
> >         d = os.path.join(os.path.dirname(numpy.__file__), '_core', 'include')
> >     else:
> >         # using installed numpy core headers
> >         import numpy._core as _core
> >         d = os.path.join(os.path.dirname(_core.__file__), 'include')
> >     return d
> 
> $ python3.11 /usr/pkgnew/bin/numpy-config-3.11 --cflags
> -I/usr/pkgnew/lib/python3.11/site-packages/numpy/_core/include
> 
> So the directory is apparently available but how to add using:
> python3.11 /usr/pkgnew/bin/numpy-config-3.11 --cflags
> ??

https://numpy.org/doc/stable/reference/distutils_status_migration.html#distutils-status-migration

Status of numpy.distutils and migration advice

numpy.distutils has been deprecated in NumPy 1.23.0. It will be removed for
Python 3.12; for Python <= 3.11 it will not be removed until 2 years after the
Python 3.12 release (Oct 2025).

Warning

numpy.distutils is only tested with setuptools < 60.0, newer versions may break.
See Interaction of numpy.distutils with setuptools for details.
Migration advice

There are several build systems which are good options to migrate to. Assuming
you have compiled code in your package (if not, you have several good options,
e.g. the build backends offered by Poetry, Hatch or PDM) and you want to be
using a well-designed, modern and reliable build system, we recommend:

    Meson, and the meson-python build backend

    CMake, and the scikit-build-core build backend

If you have modest needs (only simple Cython/C extensions; no need for Fortran,
BLAS/LAPACK, nested setup.py files, or other features of numpy.distutils) and
have been happy with numpy.distutils so far, you can also consider switching to
setuptools. Note that most functionality of numpy.distutils is unlikely to be
ported to setuptools.

--------------------

So if we stay with python3.11 for now, to deal with this problem
of py-pyside-setup not correctly including include directories,
what is the proper way to call get_numpy_include_dirs()?

DISTUTILS.rst :

Useful functions in ``numpy.distutils.misc_util``
-------------------------------------------------

+ ``get_numpy_include_dirs()`` --- return a list of NumPy base
  include directories. NumPy base include directories contain
  header files such as ``numpy/arrayobject.h``, ``numpy/funcobject.h``
  etc. For installed NumPy the returned list has length 1
  but when building NumPy the list may contain more directories,
  for example, a path to ``config.h`` file that
  ``numpy/base/setup.py`` file generates and is used by ``numpy``
  header files.