installation problem with python 3.13 and numpy 2.1

[LasseHolch]

• classy_blocks version: 1.6.4
• Python version:3.13
• Operating System: windows

Description

I received an error when installing classy-blocks.
The problem was resolved when downgrading to python 3.12 and numpy 2.0.2.
Note I'm using conda for package managing

What I Did

pip install classy-blocks                          
Collecting classy-blocks
  Using cached classy_blocks-1.6.4-py3-none-any.whl.metadata (19 kB)
Requirement already satisfied: numpy in c:\users\lahn\appdata\local\miniconda3\envs\simcaseenv\lib\site-packages (from classy-blocks) (2.1.3)
Collecting scipy (from classy-blocks)
  Using cached scipy-1.14.1-cp313-cp313-win_amd64.whl.metadata (60 kB)
Collecting nptyping (from classy-blocks)
  Using cached nptyping-2.5.0-py3-none-any.whl.metadata (7.6 kB)
Collecting numpy (from classy-blocks)
  Using cached numpy-1.26.4.tar.gz (15.8 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [21 lines of output]
      + C:\Users\LAHN\AppData\Local\miniconda3\envs\simCaseEnv\python.exe C:\Users\LAHN\AppData\Local\Temp\pip-install-_f12agz6\numpy_2c420f9862254f08ac6e29eac48a0cf4\vendored-meson\meson\meson.py setup C:\Users\LAHN\AppData\Local\
Temp\pip-install-_f12agz6\numpy_2c420f9862254f08ac6e29eac48a0cf4 C:\Users\LAHN\AppData\Local\Temp\pip-install-_f12agz6\numpy_2c420f9862254f08ac6e29eac48a0cf4\.mesonpy-xncc6ydt -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md 
--native-file=C:\Users\LAHN\AppData\Local\Temp\pip-install-_f12agz6\numpy_2c420f9862254f08ac6e29eac48a0cf4\.mesonpy-xncc6ydt\meson-python-native-file.ini
      The Meson build system
      Version: 1.2.99
      Source dir: C:\Users\LAHN\AppData\Local\Temp\pip-install-_f12agz6\numpy_2c420f9862254f08ac6e29eac48a0cf4
      Build dir: C:\Users\LAHN\AppData\Local\Temp\pip-install-_f12agz6\numpy_2c420f9862254f08ac6e29eac48a0cf4\.mesonpy-xncc6ydt
      Build type: native build
      Project name: NumPy
      Project version: 1.26.4
      WARNING: Failed to activate VS environment: Could not parse vswhere.exe output
     
      ..\meson.build:1:0: ERROR: Unknown compiler(s): [['icl'], ['cl'], ['cc'], ['gcc'], ['clang'], ['clang-cl'], ['pgcc']]
      The following exception(s) were encountered:
      Running `icl ""` gave "[WinError 2] The system cannot find the file specified"
      Running `cl /?` gave "[WinError 2] The system cannot find the file specified"
      Running `cc --version` gave "[WinError 2] The system cannot find the file specified"
      Running `gcc --version` gave "[WinError 2] The system cannot find the file specified"
      Running `clang --version` gave "[WinError 2] The system cannot find the file specified"
      Running `clang-cl /?` gave "[WinError 2] The system cannot find the file specified"
      Running `pgcc --version` gave "[WinError 2] The system cannot find the file specified"
     
      A full log can be found at C:\Users\LAHN\AppData\Local\Temp\pip-install-_f12agz6\numpy_2c420f9862254f08ac6e29eac48a0cf4\.mesonpy-xncc6ydt\meson-logs\meson-log.txt
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

[FranzBangar]

Maybe @schperplata could look into that?

[schperplata]

According to this(#62) PR and its CI pipeline, 3.13 seems to work with classy blocks, at least on linux machines provided bu GitHub Actions.
Since pip is exposing this is a numpy-related issue, could you maybe check if numpy-1.26.4 is in fact compatible with your machine? Maybe install it in a separate virtual environment, without classy blocks, directly with pip install numpy=1.26.4?

[LasseHolch]

I've tried on another machine (linux). I seems like it is a local problem of my PC. Sorry for the inconvenience.