Hi Helmut, * Helmut Grohne <hel...@subdivi.de> [2024-09-15 20:17]:
On my system, _core.file becomes "/usr/lib/python3/dist-packages/numpy/_core/__init__.py" Do you mean numpy.core rather than numpy._core? (Not sure what the difference is.)
Yeah, that has changed with NumPy 2. Quoting the release notes:
Renamed ``numpy.core`` to ``numpy._core`` -----------------------------------------Accessing ``numpy.core`` now emits a DeprecationWarning. In practice we have found that most downstream usage of ``numpy.core`` was to access functionality that is available in the main ``numpy`` namespace. If for some reason you are using functionality in ``numpy.core`` that is not available in the main ``numpy`` namespace, this means you are likely using private NumPy internals. You can still access these internals via ``numpy._core`` without a deprecation warning but we do not provide any backward compatibility guarantees for NumPy internals. Please open an issue if you think a mistake was made and something needs to be made public.
* Helmut Grohne <hel...@subdivi.de> [2024-09-15 20:17]:
Since numpy is a Python extension, I suspect that the majority of its users is building some dependent Python extension. Is there actually another way of using it? (If yes, the rest may be a bad idea.)
AFAICT, the headers are only useful/needed for Python extensions.
My favorite so far, and it seems to be working nicely, so I uploaded it to experimental.[snip]I am proposing this, because _PYTHON_SYSCONFIGDATA_NAME already is a widely established way of doing this.
Regardless of what the answer is, the question and answer should be documented in README.multiarch or something similar.
Done. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
signature.asc
Description: PGP signature
