Use Python logging instead of prints

[bitcraze-issue-importer]

Switch from using printouts to using the Python logging utility instead since it's a lot easier to filter messages and to redirect the output to a file (that can be attached to issues etc.)

The levels for the logging should correspond to:

• debug: Excessive logging (most useful for file-output)
• info: Successful events (such as "Input device 0 [PS3 controller] open for reading]")
• warning: Unsuccessful events that might cause problems (such as "Trying to set parameter [someparam] that is not in the param TOC")
• error: A serious error that will cause some functionality to fail (such as "No permission to open Crazyradio USB device")
• critical: An error that makes the application unable to continue (such as "PyQt could not be imported"). After this message the application should exit.

---

• Bitbucket: https://bitbucket.org/bitcraze/crazyflie-pc-client/issue/5
• Originally Reported By: Marcus Eliasson
• Originally Created At: 2013-02-21T15:12:36.807

[bitcraze-issue-importer]

The argument --debug or -d together with minimal, info, debug or debugfile can now be used to control the logging. The default value is info. When using minimum only warnings and errors are logged.

When using debugfile messages are also stored to a file with the some extra debug info such as thread name and time.

---

Original Comment By: Marcus Eliasson

[bitcraze-issue-importer]

Using logging instead of printouts. Close #5

→ <>

---

Original Comment By: Marcus Eliasson