[...]

I am using the python output format to get MIB module information (mainly for OID->ObjectName resolution and type information) for usage based on the PySMNP 3.5.x framework http://pysnmp.sourceforge.net. I am currently not using the range info. Therefore, I should have no problem with either change of the range info.

PySNMP 4.x has also a script (another one) that uses the smidump python output format to generate SNMP managed object classes (and MIB modules). It will probably have a problem with any change in the range info. It will be nice to inform the project maintainer of this change.

That's actually why I submitted the patch :) I am currently using libsmi2pysnmp from PySNMP 4.x. I have already posted a patch to the pysnmp mailing list that will take advantage of the python smidump changes I've provided to you. I specifically designed both patches so that nothing should break for those users who don't simultaneously upgrade both patches.

If you integrate my libsmi patch, I'm sure the pysnmp maintainers will accept by libsmi2pysnmp patch as well.

thanks, --randy