`conda install -c conda-forge modin-all` installs 0.20.1, which is not latest about modin-feedstock

[YarShev]

Workarounds are the following.

1. Install every engine separately.

conda install -c conda-forge modin-ray modin-dask modin-unidist modin-hdk

2. Install the exact version

conda install -c conda-forge modin-all=0.23.0

[h-vetinari]

The issue could also be related to using python 3.8, which is already being dropped by projects following NEP29 (and which might confuse the solver, because it doesn't know how to prioritise not-newest numpy/pandas/etc. vs. not-newest modin).

Could you try for 3.10?

[YarShev]

Python 3.10 doesn't work for me too.

[h-vetinari]

Could you post the conda list for the installation of just modin-all vs. the one for modin-all=0.23?

I just tried mamba create -n test modin-all python=3.10 on windows and it pulls in 0.23.

[YarShev]

Previously, conda pulled modin from the main channel for some reason. I had to execute the following lines to makes the things working as expected.

conda config --add channels conda-forge
conda config --set channel_priority strict

It is important to notice that I had to use mamba because conda worked very slow and I even didn't wait for the installation end with it.

[h-vetinari]

Strict channel priority is mentioned in the main readme of every feedstock - it's really the only supported way to use conda-forge packages.

Using mamba is not a bad idea either, though I guess conda would have gotten there eventually. Sidenote: the next conda release will switch to using mamba under the hood, though you can already use it with 23.7 when specifying --solver=libmamba, or (to make it permanent) conda config --set solver=libmamba.

[YarShev]

@h-vetinari, thanks, I think we can close the issue.