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
Looking at the meta package oldest-supported-numpy I see that numpy<1.18.5 will be downloaded for python 3.8 and Windows on arm64 (apart from all non-arm64 and non-aarch64 platforms).
I believe then that the check specified in pyproject.toml file will download an invalid (and unsupported by gensim) version of the NumPy library for the Windows on arm64 users:
# oldest supported Numpy for this platform is 1.17 but the oldest supported by Gensim# is 1.18.5, remove the line when they increase oldest supported Numpy for this platform"numpy==1.18.5; python_version=='3.8' and platform_machine not in 'arm64|aarch64'",
Steps/code/corpus to reproduce
As the issue is a side-effect of a discussion from a different PR (#3538 (comment)) I do not have a minimal reproducible example.
I do not have direct access to Windows on arm64 so I'll try virtualising the architecture and building gensim there. Once I'm done I'll upload the output.
Versions
Python 3.8
Windows 10
arm64 architecture
The text was updated successfully, but these errors were encountered:
Problem description
Looking at the meta package oldest-supported-numpy I see that numpy<1.18.5 will be downloaded for python 3.8 and Windows on arm64 (apart from all non-arm64 and non-aarch64 platforms).
I believe then that the check specified in pyproject.toml file will download an invalid (and unsupported by gensim) version of the NumPy library for the Windows on arm64 users:
Steps/code/corpus to reproduce
As the issue is a side-effect of a discussion from a different PR (#3538 (comment)) I do not have a minimal reproducible example.
I do not have direct access to Windows on arm64 so I'll try virtualising the architecture and building gensim there. Once I'm done I'll upload the output.
Versions
Python 3.8
Windows 10
arm64 architecture
The text was updated successfully, but these errors were encountered: