Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #12041 > unrolled thread

Python 3.8 transition: CMake problems

Back to article view | Back to linux.debian.maint.python

Contents

  Python 3.8 transition: CMake problems Ole Streicher <olebole@debian.org> - 2019-11-26 11:20 +0100
    Re: Python 3.8 transition: CMake problems Matthias Klose <doko@debian.org> - 2019-11-26 12:40 +0100

#12041 — Python 3.8 transition: CMake problems

Hi,

I am currently updating the "casacore" package to the latest upstream
version. Doing this, I discovered that it is not marked as part of the
Python 3.8 transition, and was also not binNMUed for this, although it
has the package libcasa-python3-3 (to be renamed to libcasa-python3-4)
that depends on libpython3.7. Was this somehow forgotten?

Nevertheless, when I now try to build the (updated) package, I get the
following error:

--------------------------------8<-------------------------------------
  Could NOT find Python3 (missing: Python3_LIBRARY Python3_INCLUDE_DIR
  Development NumPy) (found version "3.8.0")
Call Stack (most recent call first):
  /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.15/Modules/FindPython/Support.cmake:1653 (find_package_handle_standard_args)
  /usr/share/cmake-3.15/Modules/FindPython3.cmake:215 (include)
  python3/CMakeLists-cmake3.14.txt:3 (find_package)
--------------------------------8<-------------------------------------

The corresponding line in python3/CMakeLists-cmake3.14.txt is

find_package(Python3 REQUIRED COMPONENTS Interpreter Development NumPy)

which looks normal to me. Any idea why CMAKE does not find Python 3.8?

Best regards

Ole

[toc] | [next] | [standalone]

#12047

On 26.11.19 11:02, Ole Streicher wrote:
> Hi,
> 
> I am currently updating the "casacore" package to the latest upstream
> version. Doing this, I discovered that it is not marked as part of the
> Python 3.8 transition, and was also not binNMUed for this, although it
> has the package libcasa-python3-3 (to be renamed to libcasa-python3-4)
> that depends on libpython3.7. Was this somehow forgotten?

No. We are currently adding Python3.8 support, that's not yet switching the
default.  And the tracker only tracks packages b-d on python3-all-dev, which
casacore doesn't match, only building for the default Python3.

Matthias

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web