[GH-ISSUE #105] [Feature Request] It is recommended to change the dependency from nvidia-ml-py to pynvml #65

New issue

Closed

opened 2026-05-05 03:24:18 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 03:24:18 -06:00

Owner

Originally created by @yexcai on GitHub (Nov 16, 2023).
Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/105

Originally assigned to: @XuehaiPan on GitHub.

Required prerequisites

I have searched the Issue Tracker that this hasn't already been reported. (comment there if it has.)
I have tried the latest version of nvitop in a new isolated virtual environment.

Motivation

The ‘nvidia-ml-py’ package is outdated, and Nvidia has officially replaced it with ‘pynvml‘. Therefore, installing ’nvitop‘ (which depends on ‘nvidia-ml-py’) is not compatible with environments that depend on ‘pynvml’, such as ‘DeepSpeed’.

Solution

No response

Alternatives

No response

Additional context

No response

Originally created by @yexcai on GitHub (Nov 16, 2023). Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/105 Originally assigned to: @XuehaiPan on GitHub. ### Required prerequisites - [X] I have searched the [Issue Tracker](https://github.com/XuehaiPan/nvitop/issues) that this hasn't already been reported. (comment there if it has.) - [X] I have tried the latest version of nvitop in a new isolated virtual environment. ### Motivation The ‘nvidia-ml-py’ package is outdated, and Nvidia has officially replaced it with ‘pynvml‘. Therefore, installing ’nvitop‘ (which depends on ‘nvidia-ml-py’) is not compatible with environments that depend on ‘pynvml’, such as ‘DeepSpeed’. ### Solution _No response_ ### Alternatives _No response_ ### Additional context _No response_

gitea-mirror

2026-05-05 03:24:18 -06:00

closed this issue
added the
pynvml

enhancement

dependencies
labels

gitea-mirror commented

2026-05-05 03:24:21 -06:00

Author

Owner

@XuehaiPan commented on GitHub (Nov 16, 2023):

The ‘nvidia-ml-py’ package is outdated, and Nvidia has officially replaced it with ‘pynvml‘.

@yexcai The nvidia-ml-py package (last updated on Nov 2, 2023) is the official NVML Python bindings maintained by the NVML team.

Reference:

In the description of the pynvml PyPI package (last updated on Feb 15, 2023):

Python bindings to the NVIDIA Management Library

Provides a Python interface to GPU management and monitoring functions.

This is a wrapper around the NVML library. For information about the NVML library, see the NVML developer page http://developer.nvidia.com/nvidia-management-library-nvml

As of version 11.0.0, the NVML-wrappers used in pynvml are identical to those published through nvidia-ml-py.

In the NVML library description page https://developer.nvidia.com/nvidia-management-library-nvml:

Bindings

A set of officially supported Perl and Python bindings are available for NVML. These bindings expose the same features as the C-based interface and also provide backwards compatibility. The Perl bindings are provided via CPAN: http://search.cpan.org/%7Envbinding/nvidia-ml-pl/lib/nvidia/ml.pm and the Python bindings via PyPI: http://pypi.python.org/pypi/nvidia-ml-py.

Therefore, installing ’nvitop‘ (which depends on ‘nvidia-ml-py’) is not compatible with environments that depend on ‘pynvml’, such as ‘DeepSpeed’.

For compatibility with other packages, tt is highly recommended to install nvitop in an isolated virtual environment. You can install and run nvitop via pipx:

pipx run nvitop

@XuehaiPan commented on GitHub (Nov 16, 2023): > The ‘nvidia-ml-py’ package is outdated, and Nvidia has officially replaced it with ‘pynvml‘. @yexcai The [`nvidia-ml-py` package](https://pypi.org/project/nvidia-ml-py) (last updated on Nov 2, 2023) is the official NVML Python bindings maintained by the NVML team. Reference: In the description of the [`pynvml` PyPI package](https://pypi.org/project/pynvml) (last updated on Feb 15, 2023): > ### Python bindings to the NVIDIA Management Library > > Provides a Python interface to GPU management and monitoring functions. > > This is a wrapper around the NVML library. For information about the NVML library, see the NVML developer page http://developer.nvidia.com/nvidia-management-library-nvml > > As of version 11.0.0, the NVML-wrappers used in pynvml are identical to those published through [nvidia-ml-py](https://pypi.org/project/nvidia-ml-py/). In the NVML library description page https://developer.nvidia.com/nvidia-management-library-nvml: > ### Bindings > > A set of officially supported Perl and Python bindings are available for NVML. These bindings expose the same features as the C-based interface and also provide backwards compatibility. The Perl bindings are provided via [CPAN: http://search.cpan.org/%7Envbinding/nvidia-ml-pl/lib/nvidia/ml.pm](http://search.cpan.org/%7Envbinding/nvidia-ml-pl/lib/nvidia/ml.pm) and the Python bindings via [PyPI: http://pypi.python.org/pypi/nvidia-ml-py](http://pypi.python.org/pypi/nvidia-ml-py). ------ > Therefore, installing ’nvitop‘ (which depends on ‘nvidia-ml-py’) is not compatible with environments that depend on ‘pynvml’, such as ‘DeepSpeed’. For compatibility with other packages, tt is highly recommended to install `nvitop` in an isolated virtual environment. You can install and run `nvitop` via [`pipx`](https://pypa.github.io/pipx): ```bash pipx run nvitop ```

gitea-mirror referenced this issue

2026-05-05 03:26:44 -06:00

[PR #67] [MERGED] feat(cli): support float number as snapshot interval (>= 0.25s) #145