Better logging about qiskit HOT 7 CLOSED

Hi @hellmersjl3ds,
Thanks for offering to have a look at this. In PR#108, referenced in this PR, the python logging facility was setup and covers most of the features requested in this enhancement. One thing I think that remains to be done, however, is that the facility has not been applied everywhere (there are still print statements for instance). If you could help make the logging uniform or suggest any other improvements that would be great. For extensive changes you could open a new issue for discussion or continue using this one.

from qiskit.

Hey guys, unfortunately I'm busy with another project for the next 5 weeks or so, so I won't be able to get to this before then.

from qiskit.

What's the status of this? I see a commit from @ewinston but it's not assigned to anyone.

I'd be happy to work on it if nobody else is.

from qiskit.

Not every print call in the code should be replaced by log. Some of them need a thought. Following, a list of files in 0.4, with prints in it, and some comments for some of the cases:

• qiskit/tools/visualization.py
• qiskit/tools/qi/qi.py
• qiskit/tools/qi/pauli.py
• qiskit/tools/apps/optimization.py
• qiskit/unroll/_printerbackend.py (probably makes sense to add a file parameter, a la build-in print )
• qiskit/qasm/_qasmlexer.py: the print call in t_error maybe is an Exception (?)
• qiskit/qasm/_node/*.py: Many prints happen in to_string methods. This method should return a string instead of printing (maybe should be called __str__)
• qiskit//qasm/_qasmparser.py: The exception should be re-raised.

Currently, the testsuite do not print any of these issues (I think, it could be that the output is captured in some cases). For sure, tests are needed when performing many of these changes.

This is a very nice opportunity for a first contribution. If anybody wants to work with it and need assistance, let me know! (<- @hellmersjl3ds)

from qiskit.

Not every print call in the code should be replaced by log.

The problem of using print()statements, is that it forces the user to dump something to the stdout (usually the monitor), but this is not true for many other uses cases that printing to stdout doesn't make any sense like:

• Graphics User Interfaces (Windows apps, Mac apps, XWindows apps)
• Non-Attended devices
• *nix Daemons and Services
• ... and probably many others I'm not aware of...

We are building an SDK, so using print() is killing many use-cases we don't really want to kill.
So, basically, yes, we should replace al the prints in the code by log :)
Notice that our logger can dump to stdout like print always does, if the user requires to do so... not sure if we are exposing this functionality to the user at the moment, though.

from qiskit.

Some of the prints I mentioned are messages for an exception, for example.

from qiskit.

Ok, so after some PRs... we have included the logging system and we have removed all silent flags.
Still need to remove all presence of print() in the code, but we will create another issue to address this specific issue.
I'm going to close this Issue.

from qiskit.