The current importing mechanism relies on setting the current working directory to the proper folder ("windows-i686", "linux-i686", "linux-x86_64" or "darwin-x86_64") so the dynamic libraries can be loaded. This however doesn't work under OSX, where it expects the libraries to be in the executable folder, which will fail)
Further, the cython parts of renpy are built only for a specific python version, so it may be required to run unrpyc with the python executable in renpy.
The current importing mechanism relies on setting the current working directory to the proper folder ("windows-i686", "linux-i686", "linux-x86_64" or "darwin-x86_64") so the dynamic libraries can be loaded. This however doesn't work under OSX, where it expects the libraries to be in the executable folder, which will fail)
Further, the cython parts of renpy are built only for a specific python version, so it may be required to run unrpyc with the python executable in renpy.