Evseniia

Hi, @minrk! Could you please tell me if it is planned to fix this problem in the near future by merging this PR https://github.com/conda/conda/pull/11612?

Hello, @jaimergp @kenodegard @travishathaway! Could you please tell when it is planned to merge this PR to fix https://github.com/conda/conda/issues/11442? Do I understand correctly that this could happen in January 2023?...

I'm observing the same thing in 23.1.0: ``` Traceback (most recent call last): File "C:\Miniconda3\lib\site-packages\conda\models\version.py", line 40, in __call__ return cls._cache_[arg] KeyError: '>=0.10.0,

It looks like there are conflicts in internal CI when using numpy from conda-forge ``` The following package could not be installed └─ numpy 2.0.0 is not installable because it...

I think the reason is mkl: ``` >conda create -n numpy_v2 numpy=2.0.0 -c conda-forge The following packages will be downloaded: package | build ---------------------------|----------------- intel-openmp-2024.2.0 | h57928b3_980 1.8 MB conda-forge...

I would not add a restriction for numpy, and would just leave `"numpy",` in pyproject.toml instead of `"numpy >=1.23"` or `"numpy>=2.0.0"` in order to be able to set the numpy...

We have also already built numpy 2.0.1 for linux and I think we will finish with windows soon

In order for this PR to be built in the internal CI with 2.0, I need to change the mamba build flag to `--numpy 2.0.0`. I can try to do...

For some reason, the environment still resolved in favor of 1.26.4, even despite `--numpy 2.0.0` flag and the absence of any numpy pinning in recipe.. I believe the reason for...

@oleksandr-pavlyk **Update**: The pinning in the recipe https://github.com/IntelPython/dpctl/blob/master/pyproject.toml#L12 is always a priority compared to `--numpy `. For `--numpy ` to work as expected, the pinning should not be anywhere in...