When using the hlapi nextCmd or getCmd, there is no obvious way of checking of constraints as is possible using lookupValue=False in thepysnmp.entity.rfc3413.oneliner version.
This can make a complete smnpwalk implementation fail. Catching the PySnmpError and allowing it to pass does not allow the completion of the walk. Also, the ValueConstraintError is not raised to the level where it can be caught and handled in the hlapi.
Could a lookupValue keyword be added to the hlapi functions?
When using the hlapi
nextCmd
orgetCmd
, there is no obvious way of checking of constraints as is possible usinglookupValue=False
in thepysnmp.entity.rfc3413.oneliner
version.This can make a complete smnpwalk implementation fail. Catching the
PySnmpError
and allowing it to pass does not allow the completion of the walk. Also, theValueConstraintError
is not raised to the level where it can be caught and handled in the hlapi.Could a
lookupValue
keyword be added to the hlapi functions?