cudnnenv
cudnnenv manages various versions of cuDNN.
Requirement
Linux, macOS
Python 2.7, 3.7, 3.8, 3.9, 3.10
Install
Install cudnnenv via pip command.
$ pip install cudnnenv
Do not forget to set your environment variables. cuDNN which cudnnenv installs locates at ~/.cudnn/active/cuda.
LD_LIBRARY_PATH=~/.cudnn/active/cuda/lib64:$LD_LIBRARY_PATH CPATH=~/.cudnn/active/cuda/include:$CPATH LIBRARY_PATH=~/.cudnn/active/cuda/lib64:$LIBRARY_PATH
This program uses curl and tar commands. Please install them before you use it.
Usage
usage: cudnnenv [-h]
{install,install-file,activate,uninstall,version,versions,deactivate}
...
- positional arguments:
{install,install-file,activate,uninstall,version,versions,deactivate}
- install:
Install version
- install-file:
Install local cuDNN file
- activate:
Activate installed version
- uninstall:
Uninstall version
- version:
Show active version
- versions:
Show avalable versions
- deactivate:
Deactivate cudnnenv
- optional arguments:
- -h, --help
show this help message and exit
install
install subcommand installs a given version of cuDNN and activate it. Use activate subcommand to only activate installed version.
usage: cudnnenv install [-h] VERSION
positional arguments:
- VERSION:
Version of cuDNN you want to install and activate. Use versions subcommand to check the available versions.
install-file
install-file subcommand installs a given local cuDNN file and activate it. You can only install tar.gz file, can not use deb packages.
usage: cudnnenv install-file [-h] FILE VERSION
positional arguments:
- FILE:
Path to local cuDNN archive file to install
- VERSION:
Version name of cuDNN you want to install
activate
activate subcommand activates an installed cuDNN. This command does not download an archive file unlike install.
usage: cudnnenv activate [-h] VERSION
positional arguments:
- VERSION:
Version of installed cuDNN you want to activate.
uninstall
uninstall subcommand uninstalls a given version of cuDNN from your environment.
usage: cudnnenv uninstall [-h] VERSION
positional arguments:
- VERSION:
Version of cuDNN you want to uninstall.
version
version subcommand shows the current activated version. If you activate no version, it shows (none).
usage: cudnnenv version [-h]
versions
versions subcommand shows the available versions which you can select in install subcommand, and installed versions which you installed with install and install-files subcommands.
usage: cudnnenv versions [-h]
deactivate
deactivate subcommand deactivates cudnnenv by removing symbolic link.
usage: cudnnenv deactivate [-h]
Directory structure
+ .cudnn + versions | + v2 | | + cuda | | + include | | + lib64 | + v3 | + ... + active --> versions/vX
License
cudnnenv is distributed under MIT License.
1 maintainer
Metadata
1 maintainer
Release files for cudnnenv 0.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cudnnenv-0.8.0.tar.gz | 18.0 kB | Without provenance | Details |
Release files / cudnnenv-0.8.0.tar.gz
| Download URL | cudnnenv-0.8.0.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc66f4317758a9ab5cf8eec477e5c3ebf4cac12d6bdf9189fd42137335ea44ae
|
|
BLAKE2b-256 checksum How to use checksums |
381a757afe77441fddadf5a8e5499279297ebd45e01c4718c64ac1c87a135096
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.10
|
Security for cudnnenv 0.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
