Bug 266669 - net-mgmt/py-pysnmp: incompatibility with Python > 3.7
Summary: net-mgmt/py-pysnmp: incompatibility with Python > 3.7
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-28 05:13 UTC by O. Hartmann
Modified: 2022-09-28 05:13 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (mhjacks)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description O. Hartmann 2022-09-28 05:13:42 UTC
running several boxes with both most recent 14-CURRENT, 13-STABE and official 13.1-RELENG, I'm facing a problem utilizing port net-mgmt/py-pysnmp  (most recent ports tree, of course) in combination with Python 3.9. 
I'm playing around with Python and port net-mgmt/py-pysnmp to diff into several Cisco 4500 and 6000 type switches with a large amount of interfaces from which I'd like to retrieve informations. So far, getching single OIDs via a tutorial to be found here:

https://www.ictshore.com/sdn/python-snmp-tutorial/

I run into a serious problem and I think it's related to the fact net-mgmt/py-pysnmp is only rated to be compatible with Python up to 3.7:
Our switches report more than 500 interfaces for the department and retrieving at least 4 or 5 OIDs in a bulk request renders the bulkCmd to report crap beyond the 315th interface requested. Means, fetching ifIndex,ifDescr,ifInOctet,ifOutOctet,ifInErrors,ifOutErrors delivers on the first two OIDs just mentioned previously (no matter what order they are sent and retrieved) correct results, but with the 316th element, the OIDs starts to shift into regions of the MIB I never requested for. 1-315 are as expected. I checked on several FreeBSD flavours with no change of the behaviour as long as I use Python 3.9 or Python 3.8 (I do not have a older FBSD at hand in the network of question, nor do I have a Linux box there at hand, sorry).

The problem can be reproduced easily using recent FBSD, Python 3.9 and the above mentioned port and targeting network equipment reporting more than 315 interfaces.

I'm new to Python, so be patient if this problem is a Noob's first-blood-error.

if one can confirm the observation and the observation reveals itself a true bug, then there should be a warning since this may reveal  other serious issues.