Starting with release 0.5.4, YDK-PY is now part of the Python package index (PyPi). This means a dramatically simpler installation experience. Instead of downloading/cloning the YDK-Py code, building source packages and installing them in a particular order, you can just use the pip utility to automate the installation. Previously, a full installation of YDK-Py (YDK core package, plus XR/OpenConfig/IETF) could take 12 steps. Now, you just need to issue:
$ pip install ydk-models-cisco-ios-xr
If you already have YDK-Py installed and want to upgrade:
$ pip install ydk-models-cisco-ios-xr --upgrade
That's it. That simple!
The installation process takes care of pulling all Python dependencies and install them for you. Take into account that Python packaging doesn't handle system dependencies. That is, non-python libraries and packages required by YDK-Py or by Python packages that YDK-Py uses. You still need to install those system dependencies the first time you use YDK-Py. See our updated installation instructions in the YDK-Py documentation.If facing any issues try to verify http/https connection to other websites with the proxy config you have.
ICMP traffic is not dealt with by an HTTP proxy and Cisco websites are usually not routed via the lab proxies. Can you use curl or wget with external websites.
on lab machines use proxy.esl.cisco.com:80<http://proxy.esl.cisco.com:80> as the setting and that works fine. For example:
- export http_proxy=http://proxy.esl.cisco.com:80/
- export https_proxy=http://proxy.esl.cisco.com:80/
- export ftp_proxy=http://proxy.esl.cisco.com:80/
- export no_proxy=.cisco.com<http://cisco.com>
- export HTTP_PROXY=http://proxy.esl.cisco.com:80/
- export HTTPS_PROXY=http://proxy.esl.cisco.com:80/
- export FTP_PROXY=http://proxy.esl.cisco.com:80/