With some signatures, the initialization of the NETCONF provider in YDK-Py doesn't handle gracefully the condition where port=None. Those cases break backward compatibility with pre-0.6.0 releases and introduce inconsistency in the handling of this argument in the different NETCONF provider signatures in YDK-Py 0.6.0.
With some signatures, the initialization of the NETCONF provider in YDK-Py doesn't handle gracefully the condition where
port=None. Those cases break backward compatibility with pre-0.6.0 releases and introduce inconsistency in the handling of this argument in the different NETCONF provider signatures in YDK-Py 0.6.0.