raylib-py 4.2.0.post2

Package release for the C Raylib 4.2 Post-Release 2

This release was made as output of another project, as mentioned in #45.

Added:

• Custom library loading: load a custom lib binary when importing raylib-py:

  You may add a .raylib file to specify custom binaries to be loaded. How it works:

  • Create a .raylib file with the following contents:

    {
        "win32": {
            "64bit": "path/to/my/custom/win32/binary/filename.ext"
        },
        "linux": {
            "64bit": "path/to/my/custom/linux/binary/filename.ext",
            "32bit": "path/to/my/custom/linux/binary/filename.ext"
        },
        "darwin": {
            "64bit": "path/to/my/custom/macos/binary/filename.ext"
        }
    }

    Omit platforms or architectures you don't want/have a custom binary for; the default binaries will be loaded instead. The file is not inspected for any extra content.

  • Before importing raylib-py, make sure the current working directory points to where .raylib is located in your project.

    If .raylib is found, it will look for the binary path for the system platform and arch and try to load it.

    If the .raylib is invalid JSON, it will fallback to the default binary.

    If the binary is not found, it won't fallback to the default binary.

    No path manipulations like os.path.join(...) are made.

Fixes:

• Fixed some swizzling errors on Rectangle

Known Issues:

• Callback for logging will not work
• Functions with vararg will not work
• Avoid string manipulation functions
• Some examples are broken due to API changes
• For some unknown reason, the 32bit binary for Linux is not available.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg