PySNMP ecosystem has been idle ever since 2020, and while many repos were forked by different parties, none of the authors showed a plan to completely take over the ecosystem as a whole and bring the repos forward,
https://github.com/pysnmp has forked several key components (#416) and published several new releases mainly for a Splunk project. No documentation site was planned for this.
https://github.com/inexio has forked most of the components to maintain a documentation mirror (#389) at https://snmplabs.thola.io/. However, contents on this site do not map to released versions of the packages, so you might hit breaking pieces here and there.
Note that inexio GmbH was once the sponsor of Ilya.
Simon Fagerholm used his fork to create https://pysnmp.readthedocs.io/ but he made no other commits. Thus, this doc site while high in search engine results contains out-of-date information and does not really help much.
Other forks didn't show significant progress.
The primary domain name (snmplabs.com) was lost and fell into the hands of unknown. The current owner(s) never reveals the identity, so any connection to that domain can be risky for general public.
New Python releases (3.11 and 3.12 for example) introduced breaking changes that impact PySNMP 4.x users significantly (for example, changes related to asyncio and asyncore).
As Ilya passed away (#427), I think it is more important than ever to regroup all parties under the same banner.
My company LeXtudio Inc. has been active in SNMP field for more than a decade now, mainly focusing on its .NET ecosystem. But some clients asked if we can support PySNMP for them, so we asked ourselves why not take the lead to revive PySNMP.
[x] Add unit test coverage to help reveal new/known bugs and ensure patches work as expected.
[x] Add compatibility test to support all major Python releases (3.8+, in Feb 2024)
[ ] (in-progress) Help downstream projects upgrade to 6.0 releases (OpenStack, Home Assistant, etc).
[ ] (in-progress) PEP 541 request to take over the remaining 11 PyPI packages (pysnmp*/pysmi/snmp*) from Ilya. Please leave your comments and help move the slow PEP 541 process forward.
[ ] (in-progress) Review and cherry pick all existing patches (2020-2022)
[ ] (in-progress) Review and close most existing issues reported (2020-2022), tracked in lextudio/pysnmp/issues/4
In the long run, LeXtudio Inc. plans to work with key stakeholders (projects that depend on pysnmp) and sponsors to set up the governing rules around the repos. Ideally there should be a PySNMP organization that supervises the development.
Known Projects Switched to LeXtudio Fork
This is not a complete list but can show you the momentum.
PEP 541 request was opened for us to take over the remaining PyPI packages (pysnmp*/pysmi/snmp*) from Ilya. Please leave your comments there and help move the slow PEP 541 process forward.
Sponsor this initiative to revive the ecosystem by contacting support@lextudio.com if you like to offer financial support to speed up the process.
Write to support@lextudio.com if you want to offer other kind of assistance (code review, documentation, and others).
Background
PySNMP ecosystem has been idle ever since 2020, and while many repos were forked by different parties, none of the authors showed a plan to completely take over the ecosystem as a whole and bring the repos forward,
pyasn1*. https://pyasn1.readthedocs.io/ was set up and matches the new releases.As Ilya passed away (#427), I think it is more important than ever to regroup all parties under the same banner.
My company LeXtudio Inc. has been active in SNMP field for more than a decade now, mainly focusing on its .NET ecosystem. But some clients asked if we can support PySNMP for them, so we asked ourselves why not take the lead to revive PySNMP.
Migration Plan
[x] Publish new releases of the Python packages.
pysnmp*/pysmi/snmp*) from Ilya. Please leave your comments and help move the slow PEP 541 process forward.In the long run, LeXtudio Inc. plans to work with key stakeholders (projects that depend on pysnmp) and sponsors to set up the governing rules around the repos. Ideally there should be a PySNMP organization that supervises the development.
Known Projects Switched to LeXtudio Fork
You Can Help
What help is needed from you?
pysnmp*/pysmi/snmp*) from Ilya. Please leave your comments there and help move the slow PEP 541 process forward.