Package: nanobind-dev Version: 1.9.2-1 Severity: normal X-Debbugs-Cc: francesco.balla...@unicatt.it, dpars...@debian.org
Dear Maintainer, I would like to ask two questions related on usage of nanobind-dev from python: 1) The user guide at https://nanobind.readthedocs.io/en/latest/building.html#finding-nanobind states that the downstream user should query python3 -m nanobind --cmake_dir to determine where nanobind is installed. However, this is not currently possible with nanobind-dev, since the file __init__.py is not installed among the standard python paths. To make this work, one has to use PYTHONPATH=/usr/share python3 -m nanobind --cmake_dir 2) Downstream users or packages may have a pyproject.toml file which contains ============ [build-system] requires = ["nanobind"] ============ When building with --no-build-isolation, this requires the nanobind-*.dist-info folder to be present. Currently either pip3 show nanobind or PYTHONPATH=/usr/share pip3 show nanobind show WARNING: Package(s) not found: nanobind while nanobind installed from pypi.org would show something like ============ Name: nanobind Version: 1.9.2 Summary: nanobind: tiny and efficient C++/Python bindings Home-page: https://github.com/wjakob/nanobind Author: Wenzel Jakob Author-email: wenzel.ja...@epfl.ch License: BSD Location: /usr/local/lib/python3.11/dist-packages Requires: Required-by: ============= The next version of fenics-dolfinx, to be packaged in Debian upon release, will require --no-build-isolation and nanobind. Thanks, Francesco -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages nanobind-dev depends on: ii libeigen3-dev 3.4.0-4 ii robin-map-dev 1.2.1-1 nanobind-dev recommends no packages. nanobind-dev suggests no packages. -- no debconf information
