-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V7.1.6 Change of PEP8 naming convention has broken many functions (breaking backwards compatability) #132
Comments
New issues are marked as low priority by default. Becoming our commercial customers, and then your reports are handled with higher priority after triage. |
Currently we mainly rely on the commercial customers to report compatibility issues, so reports like this indicate that unfortunately gaps exist and will last for a while. You might try out the 7.1.7 release where we fixed some of these bugs. But we expect more similar issues to be reported. We plan to address such by shipping more frequent releases throughout the 7.1.x cycle, till we feel it's safe to ship 8.0 with all compatibility layer removed. |
@lextm thanks for putting in a fix to the issue.
Am I missing something here? |
@WibblyGhost We currently possess a substantial inventory of MIB documents for testing. The latest version, 1.5.4, has shown decent performance with approximately 1,000 failed modules out of over 11,000 files. Our current focus is on addressing the requirements of the commercial clients and we may extend testing to other requests like yours afterwards. Any necessary fixes will be incorporated into upcoming releases of pysmi. |
Expected behavior
I should be able to run any PySNMP functions, but cannot.
Actual behavior
When updating to the latest version 7.1.6 of PySNMP, it seems to have broken all backwards compatability due to the commit that updates all functions to PEP8 compliance (which I agree is important), but testing has not been performed when pushing this release as it breaks all functions in PySNMP, and also breaks our custom MIB's created through PySMI's mibdump.
And our custom mibs created using the latest pysmi-lexstudio (1.4.3) also don't follow the new PEP8 naming convention change.
Or maybe I'm suppsoed to use pysmi (7.1.6) which has the following errors...
Detailed steps
The steps are,
Try run PySNMP
or
Try run custom MIBS with PySNMP
Python package information
7.1.6
Operating system information
Ubuntu
Python information
3.12
(Optional) Contents of your test script
No response
Relevant log output
The text was updated successfully, but these errors were encountered: