You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, just noticed that current build pyradiance-0.4.1-py3-none-macosx_11_0_arm64.whl from pypi seems to have both arm64 and intel x86_64 binaries in it.
Is it intentional and it should be named _universal2.whl instead of _arm64.whl then? Or it's a bug and it should have only arm64 binaries?
libraycalls.so is the shared library for Radiance C function calls and they might be universal due to the way it's created, but I have not tested.
Majority of the function however uses binaries inside the bin directory and those should be arch specific.
Hi, just noticed that current build
pyradiance-0.4.1-py3-none-macosx_11_0_arm64.whl
from pypi seems to have both arm64 and intel x86_64 binaries in it.Is it intentional and it should be named
_universal2.whl
instead of_arm64.whl
then? Or it's a bug and it should have only arm64 binaries?The text was updated successfully, but these errors were encountered: