-
Notifications
You must be signed in to change notification settings - Fork 58
Latest version on Pypi #3
Comments
In the meantime you can do something like
|
Yeah, this is what we have. The main problem is that the version number in this repo is the same as in PyPi, so it won't automatically update to this version of nvidia-ml-py3 if it already exists on their system (this is for a requirements.txt install). I have had to fork this repo to update the version number. It also means it also re-downloads the git version every time people try to update to check the version number. |
This doesn't work well with other libraries that depend on this library. |
Would be quite helpful if the pypi version was updated. |
I'd suggest to ping or email repository owner directly for that. Not everyone has github comment notifications enabled. |
do you have his email address? github doesn't expose repo owner's email address. |
It looks like NVIDIA has also updated their bindings on PyPi Edit: This is highly related: gpuopenanalytics/pynvml#2. |
As of 2021, there is no need to use this library or NVIDIA is maintaining an official python binding (which also is compatible with python3): https://pypi.org/project/nvidia-ml-py/ FYI as of today the latest version is 11.460.79 which is released on May 2021, including recent changes to the NVML API. Regarding Patrik's comment, there is a bit hiccup in package versions, see also: https://forums.developer.nvidia.com/t/mistake-with-nvidia-ml-py-on-pypi/112942 for more details. NVIDIA will remove the 375.xx package soon. For now, you can do:
@nicolargo Could you please consider informing this information in the repository? |
First up, thanks for this extremely useful Lib.
I was wondering if it would be possible to push the latest version with the check into System32 for Windows users to PyPi?
It seems that Windows is increasingly installing Nvidia drivers this way, and it would be extremely useful to be able to pull this functionality in with Pip.
Many thanks, and keep up the good work!
The text was updated successfully, but these errors were encountered: