Thanks (Was: pyarrow: Could NOT find Python3 (missing: Python3_LIBRARIES Python3_INCLUDE_DIRS))
On Wed, Jul 22, 2020 at 09:43:01AM -0400, Scott Talbert wrote: > > Any idea why these variables are not sensibly set automatically and what > > I can do to provide these? > > Try adding python3-all-dev to Build-Depends. Thanks - that was simple. ;-) Kind regards, Andreas. -- http://fam-tille.de
Re: pyarrow: Could NOT find Python3 (missing: Python3_LIBRARIES Python3_INCLUDE_DIRS)
On Wed, 22 Jul 2020, Andreas Tille wrote: Hi, I intend to package pyarrow[1] as a precondition for some Debian Med package. Unfortunately I get: ... -- Build output directory: /build/python-pyarrow-0.17.1/build/temp.linux-x86_64-3.8/release CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message): Could NOT find Python3 (missing: Python3_LIBRARIES Python3_INCLUDE_DIRS Development NumPy) (found version "3.8.5") Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.16/Modules/FindPython/Support.cmake:2214 (find_package_handle_standard_args) /usr/share/cmake-3.16/Modules/FindPython3.cmake:300 (include) cmake_modules/FindPython3Alt.cmake:46 (find_package) CMakeLists.txt:196 (find_package) -- Configuring incomplete, errors occurred! See also "/build/python-pyarrow-0.17.1/build/temp.linux-x86_64-3.8/CMakeFiles/CMakeOutput.log". error: command 'cmake' failed with exit status 1 Any idea why these variables are not sensibly set automatically and what I can do to provide these? Try adding python3-all-dev to Build-Depends. Scott
pyarrow: Could NOT find Python3 (missing: Python3_LIBRARIES Python3_INCLUDE_DIRS)
Hi, I intend to package pyarrow[1] as a precondition for some Debian Med package. Unfortunately I get: ... -- Build output directory: /build/python-pyarrow-0.17.1/build/temp.linux-x86_64-3.8/release CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message): Could NOT find Python3 (missing: Python3_LIBRARIES Python3_INCLUDE_DIRS Development NumPy) (found version "3.8.5") Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.16/Modules/FindPython/Support.cmake:2214 (find_package_handle_standard_args) /usr/share/cmake-3.16/Modules/FindPython3.cmake:300 (include) cmake_modules/FindPython3Alt.cmake:46 (find_package) CMakeLists.txt:196 (find_package) -- Configuring incomplete, errors occurred! See also "/build/python-pyarrow-0.17.1/build/temp.linux-x86_64-3.8/CMakeFiles/CMakeOutput.log". error: command 'cmake' failed with exit status 1 Any idea why these variables are not sensibly set automatically and what I can do to provide these? Kind regards Andreas. [1] https://salsa.debian.org/med-team/python-pyarrow -- http://fam-tille.de
Bug#966019: RFP: python-gsd -- native file format for HOOMD-blue
Package: wnpp Severity: wishlist X-Debbugs-Cc: debichem-de...@lists.alioth.debian.org, debian-scie...@lists.debian.org, debian-python@lists.debian.org Control: block 962440 by -1 * Package name: python-gsd Version : 2.1.2 Upstream Author : Joshua A. Anderson et al, University of Michigan * URL : https://gsd.readthedocs.io * License : BSD-2 Programming Lang: Python Description : native file format for HOOMD-blue The GSD file format is the native file format for HOOMD-blue. GSD files store trajectories of the HOOMD-blue system state in a binary file with efficient random access to frames. GSD allows all particle and topology properties to vary from one frame to the next. Use the GSD Python API to specify the initial condition for a HOOMD-blue simulation or analyze trajectory output with a script. Read a GSD trajectory with a visualization tool to explore the behavior of the simulation. Required by mdanalysis. Suitable for package within the Debichem team, but the Debian Science Team or Debian Python Module Team could also maintain it.
