[FEAT]: Better error handling with more verbose error messages

[nfelt14]

Description

It would be nice if the failures printed out by methods similar to query_response() could print out a little more information and use some common code for raising and formatting errors.

Additional Information

No response

[nfelt14]

The goal here is to make all errors and most exceptions easier to understand for the end-user.

[nfelt14]

As well as reduce the amount of "noise" in the errors. Some of them will need to be made smaller.

[nfelt14]

Things to do:

1. Add more information about solutions/debugging/etc. to areas that are known to be more error prone (connection, write/query, etc.)
2. catch errors and remove "noise", just keep the information we need

[nfelt14]

One idea is to pipe the stacktrace of the third-party libraries (pyvisa, etc.) into the log file with the DEBUG logging level. Then the stdout/stderr could just show the understandable error/exception message.

This only applies to the areas where we know there are bound to be errors, since this is Python, it isn't possible to account for all potential uncaught exceptions.

[nfelt14]

Areas of code to work on:

• connection
• write
• query
• read
• set_and_check
• query_response (and other similar methods)
• logging configuration (provide an opt-out of the exception logging)

[nfelt14]

Released in v3.1