pysnmp under new ownership with breaking compatilbility
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 836
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Description
Describe the bug
The pysnmp module has a new organization owning the package. https://pypi.org/project/pysnmp/.
See information on the history here: https://docs.lextudio.com/snmp/history
It appears the API has also changed significantly with this change of owner. This breaks the Bandit checks on the old package signature.
Reproduction steps
Can no longer import CommunityData as before.
>>> from pysnmp.hlapi import CommunityData
Traceback (most recent call last):
File "<python-input-8>", line 1, in <module>
from pysnmp.hlapi import CommunityData
Expected behavior
Should import as before.
Bandit version
1.8.3 (Default)
Python version
3.13 (Default)
Additional context
https://docs.lextudio.com/pysnmp/v7.1/upgrade
https://github.com/lextudio/pysnmp/blob/main/SECURITY.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the CommunityData import failure with Python 3.13 and compare the current pysnmp API with the v7.1 upgrade documentation. Then locate the Bandit check that depends on the old package signature; done means the check works with the new ownership/API while preserving its intended behavior and tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100