"The problem is that python throws an ugly-to-read and completly senseless backtrace to the novice (end!) user by default."

Oh ok, I changed the title of the issue.

"Backtraces are great for debugging and should be treated as such, but not presented to an end user by default."

We may hide the traceback by default or even do not write anything by default, and write the traceback when -v option is used.

We may hide the traceback when -q is used.