Use PyNVML 11 for now

PyNVML 12 will depend on nvidia-ml-py and drop its equivalent
functionality. So it will largely become a metapackage with some
utilities. This will mean using a much newer version of the NVML
functionality through Python than is currently used in RAPIDS. As a
preventive step, stick to PyNVML 11, which is what RAPIDS already uses.

Then when PyNVML 12 is released, this can be relaxed on a
project-by-project basis to see if it unconvers any issues that will
need project-level fixes.

conda/environments/all_arch-any.yaml

@@ -10,7 +10,7 @@ dependencies:
 - nodejs=18
 - pre-commit
 - psutil
-- pynvml
+- pynvml>=11.0.0,<12.0.0a0
 - pytest
 - pytest-asyncio
 - pytest-jupyter[server]>=0.6.0

conda/recipes/jupyterlab-nvdashboard/meta.yaml

@@ -26,7 +26,7 @@ requirements:
   run:
     - python >=3.8
     - jupyterlab >=4
-    - pynvml
+    - pynvml >=11.0.0,<12.0.0a0
     - psutil
 
 

dependencies.yaml

@@ -72,7 +72,7 @@ dependencies:
       - output_types: [conda, requirements, pyproject]
         packages:
           - jupyterlab>=4
-          - pynvml
+          - pynvml>=11.0.0,<12.0.0a0
           - psutil
   test_python:
     common:

pyproject.toml

@@ -31,7 +31,7 @@ classifiers = [
 dependencies = [
     "jupyterlab>=4",
     "psutil",
-    "pynvml",
+    "pynvml>=11.0.0,<12.0.0a0",
 ] # This list was generated by `rapids-dependency-file-generator`. To make changes, edit dependencies.yaml and run `rapids-dependency-file-generator`.
 dynamic = ["version", "description", "authors", "urls", "keywords"]