Installation issue: GPy

[momutassem]

when installing the extra-requirements.txt, I get the following issue:

GPy/kern/src/stationary_cython.c:196:12: fatal error: 'longintrepr.h' file not found
#include "longintrepr.h"
^~~~~~~~~~~~~~~
1 error generated.
error: command '/usr/bin/clang' failed with exit code 1
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for GPy
Failed to build GPy
ERROR: Could not build wheels for GPy, which is required to install pyproject.toml-based projects

[mravanelli]

@momutassem, you are referring to which of the three benchmarks currently available?

[vmcru]

I also get this error with MOABB

Failed to build GPy
ERROR: Could not build wheels for GPy, which is required to install pyproject.toml-based projects

And more here:

 _Warning: Package 'GPy.kern.src.todo' is absent from the `packages` configuration.
      !!
      
              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'GPy.kern.src.todo' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.
      
              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'GPy.kern.src.todo' is explicitly added
              to the `packages` configuration field.
      
              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).
      
              You can read more about "package discovery" on setuptools documentation page:
      
              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
      
              If you don't want 'GPy.kern.src.todo' to be distributed and are
              already explicitly excluding 'GPy.kern.src.todo' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.
      
              You can read more about "package data files" on setuptools documentation page:
      
              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
      
      
              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************
      
      !!

[momutassem]

@momutassem, you are referring to which of the three benchmarks currently available?

The MOABB benchmark.

[mravanelli]

This might depend on your specific environment. I tried on three different machines and I cannot reproduce. For instance, if you use Colab everything is running: https://drive.google.com/file/d/1x3kNX65FelDhyl6ooNyFK8pVXsLxTm_N/view?usp=sharing . One suggestion is to install gpy with conda rather than with pip: conda install conda-forge::gpy

…

On Thu, Feb 15, 2024 at 1:28 PM momutassem ***@***.***> wrote: @momutassem <https://github.com/momutassem>, you are referring to which of the three benchmarks currently available? The MOABB benchmark. — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEA2ZVSSXUKNCFKT3HJS3SLYTZHVPAVCNFSM6AAAAABDG2ORU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBWHA3TQNJZGY> . You are receiving this because you commented.Message ID: ***@***.***>

[momutassem]

Okay great, it’s working now. Thank you for your help!

[mravanelli]

Which changes did you do in your environment to make it working?

…

On Sun, Feb 18, 2024 at 12:00 PM momutassem ***@***.***> wrote: Okay great, it’s working now. Thank you for your help! — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEA2ZVUB23RKVZKYAMPH4WDYUIXT3AVCNFSM6AAAAABDG2ORU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGM4DKNRSGM> . You are receiving this because you commented.Message ID: ***@***.***>

[Drew-Wagner]

I had the same problem and resolved it by downgrading from python 3.11 to python 3.10

[mravanelli]

I added a warning into the README to notify that to the users. Personally, I'm able to make it working with python 3.11 as well, but it looks like other users have issues with that.

[momutassem]

I was also able to make it work with python 3.11 by just installing it directly using pip.