Bug#1067085: nanobind-dev not in python path and without distribution info

[Timo Röhling]

Hi,

On Mon, 18 Mar 2024 08:16:33 +0000 Francesco Ballarin <francesco.balla...@unicatt.it> wrote:

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.

The `python3 -m nanobind --cmake_dir` call is only needed for the pip/conda package because it installs the CMake config in a location that is not searched by default. It is not necessary for the Debian package -- find_package(nanobind) works out of the box -- but does not hurt (much) either.

2) Downstream users or packages may have a pyproject.toml file which

contains
============
[build-system]
requires = ["nanobind"]
============

I added a new binary package python3-nanobind, which provides the nanobind module for this use case. Technically, it is not needed for the reason outlined above, but if it makes life easier for downstream users, that's good enough for me.

Cheers
Timo


--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

signature.asc
Description: PGP signature