Hi Dima, * Dima Kogan <dko...@debian.org> [2024-03-20 18:23]:
I removed that symlink in the latest release, because it is not created by upstream but a Debian specific patch, and according to #998084 [1], it can badly interfere with venv setups.Can we get that symlink back, please?
I would very much prefer if other Debian packages used the canonical way of discovering NumPy include directories, i.e., numpy.get_include(). Starting with NumPy 2.0, there will be a pkgconf file available, too.
That being said, I can temporarily reinstate the symlinks if you cannot fix the issue on your side in a timely manner, but I'd like them gone for the trixie release.
How do you wish to proceed? Cheers Timo [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998084 -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
signature.asc
Description: PGP signature
