5.5 release contains 5.0 dynamic libs

[mlow]

$ source venv/bin/activate
$ pip install raylib-py==5.5.0
$ python3 -c 'import raylibpy' 
Library loading info:
        platform: linux
        bitness: 64bit
        current working dir: /src/game
        .raylib used: no
        .raylib status: INFO: .raylib file not available
        absolute path: /src/game/venv/lib/python3.13/site-packages/raylibpy/bin/64bit/libraylib.so.5.5.0
        is extension: no
        path exists: no
        path leads to a file: no

Traceback (most recent call last):
  File "/src/game/main.py", line 5, in <module>
    import raylibpy as rl
  File "/src/game/venv/lib/python3.13/site-packages/raylibpy/__init__.py", line 1898, in <module>
    rlapi = _load_library('raylib', False, ['{}/bin'], win32='raylib.dll', linux='libraylib.so.5.5.0', darwin='libraylib.5.5.0.dylib')
  File "/src/game/venv/lib/python3.13/site-packages/raylibpy/__init__.py", line 1887, in _load_library
    lib_ = CDLL(_lib_fname_abspath)
  File "/usr/lib/python3.13/ctypes/__init__.py", line 390, in __init__
    self._handle = _dlopen(self._name, mode)
                   ~~~~~~~^^^^^^^^^^^^^^^^^^
OSError: /src/game/venv/lib/python3.13/site-packages/raylibpy/bin/64bit/libraylib.so.5.5.0: cannot open shared object file: No such file or directory
$ ls venv/lib/python3.13/site-packages/raylibpy/bin/64bit/
libraylib.5.0.0.dylib  libraylib.so.5.0.0  raylib.dll  testlib.dll

I can get around this by placing the expected .so file into the /src/game/venv/lib/python3.13/site-packages/raylibpy/bin/64bit/ directory.

[jwannamaker]

I'm getting this issue, although I'm not entirely sure what you mean by "placing the expected .so file into the expected directory".

[mlow]

@jwannamaker In the case above, it's looking for /src/game/venv/lib/python3.13/site-packages/raylibpy/bin/64bit/libraylib.so.5.5.0. So I downloaded raylib 5.5, and extracted its libraylib.so.5.5.0 to that location