[ net-snmp-Bugs-3394081 ] Use exceptions rather than printing to stderr

[SourceForge.net <no...@so...>]

Bugs item #3394081, was opened at 2011-08-18 10:56
Message generated for change (Comment added) made by hardaker
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=3394081&group_id=12694

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: python
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Use exceptions rather than printing to stderr

Initial Comment:
I've noticed at least one place (client.py) where an error condition is handled by printing a message to stderr.  This is a completely inappropriate action for a library to take.  Please raise exceptions instead, so we have a way to handle the error in our application.

This applies to all available versions that I can see.

----------------------------------------------------------------------

>Comment By: Wes Hardaker (hardaker)
Date: 2011-08-25 06:52

Message:
We'd gladly accept a patch!

(in the mean time the bug will stay open until fixed of course.  It's
probably worth noting that because the python module is a wrapper around
the base library, that you'll always get stuff printed to the logging
output (stderr or otherwise) because the base Net-SNMP C library will be
logging well below the python layer and can't throw exceptions).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=3394081&group_id=12694