init renv and environment problem

[Bassel-kh]

This form is only for bug reports. For questions, feature requests, or feedback use our Github discussions

• [ ] OS version ( Windows 10) when excute : conda env create -f environment.yml -n MY_ENV_NAME i get this: how to solve this problem ResolvePackageNotFound:
  • libedit=3.1.20191231
  • xgboost=0.90
  • libcxx=10.0.0
  • ncurses=6.2
  • readline=8.0
  • libgfortran

[Bassel-kh]

i used this env yml for me: name: rapids23 channels:

• defaults dependencies:
• _py-xgboost-mutex=2.0=cpu_0
• blas=1.0=mkl
• brotlipy=0.7.0=py37h2bbff1b_1003
• bzip2=1.0.8=he774522_0
• ca-certificates=2023.05.30=haa95532_0
• certifi=2022.12.7=py37haa95532_0
• cffi=1.15.1=py37h2bbff1b_3
• cryptography=39.0.1=py37h21b164f_0
• idna=3.4=py37haa95532_0
• intel-openmp=2021.4.0=haa95532_3556
• ipython_genutils=0.2.0=pyhd3eb1b0_1
• libffi=3.2.1=ha925a31_1007
• libxgboost=0.90=1
• m2w64-gcc-libgfortran=5.3.0=6
• m2w64-gcc-libs=5.3.0=7
• m2w64-gcc-libs-core=5.3.0=7
• m2w64-gmp=6.1.0=2
• m2w64-libwinpthread-git=5.0.0.4634.697f757=2
• mkl=2021.4.0=haa95532_640
• mkl-service=2.4.0=py37h2bbff1b_0
• mkl_fft=1.3.1=py37h277e83a_0
• mkl_random=1.2.2=py37hf11a4ad_0
• msys2-conda-epoch=20160418=1
• numpy=1.21.5=py37h7a0a035_3
• numpy-base=1.21.5=py37hca35cd5_3
• openssl=1.1.1u=h2bbff1b_0
• pandas=1.1.5=py37hf11a4ad_0
• pip=22.3.1=py37haa95532_0
• pycparser=2.21=pyhd3eb1b0_0
• pyopenssl=23.0.0=py37haa95532_0
• pyparsing=2.4.7=pyhd3eb1b0_0
• pysocks=1.7.1=py37_1
• python=3.7.9=h60c2a47_0
• python-dateutil=2.8.2=pyhd3eb1b0_0
• pytz=2022.7=py37haa95532_0
• setuptools=65.6.3=py37haa95532_0
• six=1.15.0=py37haa95532_0
• sqlite=3.33.0=h2a8f88b_0
• tk=8.6.10=he774522_0
• urllib3=1.25.11=py_0
• vc=14.2=h21ff451_1
• vs2015_runtime=14.27.29016=h5e58377_2
• wheel=0.36.2=pyhd3eb1b0_0
• whichcraft=0.6.1=pyhd3eb1b0_0
• win_inet_pton=1.1.0=py37haa95532_0
• wincertstore=0.2=py37haa95532_2
• wrapt=1.12.1=py37he774522_1
• xz=5.2.5=h8cc25b3_1
• yaml=0.2.5=he774522_0
• zipp=3.4.0=pyhd3eb1b0_0
• zlib=1.2.13=h8cc25b3_0
• pip:
  • amply==0.1.4
  • appdirs==1.4.4
  • attrs==23.1.0
  • charset-normalizer==3.2.0
  • configargparse==0.15.1
  • datrie==0.8.2
  • decorator==4.4.2
  • docutils==0.20.1
  • gitdb==4.0.10
  • gitpython==3.1.32
  • imbalanced-learn==0.6.2
  • importlib-metadata==6.7.0
  • importlib-resources==5.12.0
  • jinja2==2.11.2
  • jsonschema==4.17.3
  • jupyter-core==4.6.3
  • nbformat==5.0.7
  • pkgutil-resolve-name==1.3.10
  • psutil==5.9.5
  • pulp==2.7.0
  • pyrsistent==0.19.3
  • pythran-openblas==0.3.6
  • pywin32==306
  • pyyaml==6.0.1
  • ratelimiter==1.2.0.post0
  • requests==2.31.0
  • smmap==5.0.0
  • snakemake==5.30.2
  • toposort==1.5
  • traitlets==5.9.0
  • typing-extensions==4.7.1 prefix: C:\Users\HP_VI\miniconda3\envs\rapids23

[jenniferfedor]

Hi @Bassel-kh, thank you for using RAPIDS and for reporting this issue and your solution! One of our interns has been looking into this and was able to reproduce the issue on a machine running Windows 11 (unfortunately our team does not currently have a machine with Windows 10 available to us). Our intern was also able to restore the Python virtual environment by updating the environment.yml file as you describe. However, with this updated environment, some of our tests fail and thus the results RAPIDS produces under these conditions are likely to be different than expected. We wanted to make sure you were aware of this.

As we mention in our documentation, RAPIDS does not officially support native installation on Windows, so in light of this and other potential issues, we highly recommend that you instead run RAPIDS through WSL or our Docker container if either of those options are available to you.