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
I believe that specifying scipy as a build-only dependency is unnecessary.
Pip builds the library in isolated environment (by default) where it first downloads (and alternatively builds) build-only dependencies. This behaviour creates additional problems for architectures for which there are not many .whl distributions, like e.g. ppc64le.
Steps/code/corpus to reproduce
create an environment where there is already an older scipy library version installed
cd gensim/
pip install .
As there is no gensim.whl distribution for ppc64le, pip will try building gensim in a new isolated environment with build-only dependencies.
As there is no scipy.whl distribution for ppc64le either, pip will try building that as well.
Despite the fact that scipy is already installed in desired version within the target environment.
Not only there will be a scipy version mismatch (pip will be building the latest version in the isolated environment) but it will also:
significantly prolong the install phase, as scipy takes relatively long to build from source,
create additional dependencies mess, as scipy build requires multiple other dependencies and system-level libraries
Desired resolution
I've tested locally installing gensim with modified pyproject.toml file (deleted scipy) and it works as expected.
Is there any other logic that does not allow deleting scipy as a build-only dependency?
Versions
gensim>4.3.*
The text was updated successfully, but these errors were encountered:
Problem description
I believe that specifying
scipy
as a build-only dependency is unnecessary.Pip builds the library in isolated environment (by default) where it first downloads (and alternatively builds) build-only dependencies. This behaviour creates additional problems for architectures for which there are not many .whl distributions, like e.g. ppc64le.
Steps/code/corpus to reproduce
create an environment where there is already an older
scipy
library version installedgensim
.whl distribution for ppc64le, pip will try buildinggensim
in a new isolated environment with build-only dependencies.As there is no
scipy
.whl distribution for ppc64le either, pip will try building that as well.Despite the fact that
scipy
is already installed in desired version within the target environment.Not only there will be a
scipy
version mismatch (pip will be building the latest version in the isolated environment) but it will also:scipy
takes relatively long to build from source,scipy
build requires multiple other dependencies and system-level librariesDesired resolution
I've tested locally installing gensim with modified
pyproject.toml
file (deletedscipy
) and it works as expected.Is there any other logic that does not allow deleting
scipy
as a build-only dependency?Versions
gensim>4.3.*
The text was updated successfully, but these errors were encountered: