Peter M. Groen / oletools

Ppt parser

… handling, JSON output)

(to easily see where log output comes from if ppt_parser is used from olevba)

Qapla'

…ype and DocumentContainer

also ran through pylint

rather non-atomic, sorry

no need to do error/exception output here since an error is raised anyway
if opening/processing failed and otherwise the error is not so bad (e.g.
one opening attempt failed but next succeeds for same file)

--> main or other caller can better control the output (e.g. for json/triage mode)

Added a few debug-traces

re-use old debug-function print_json for proper purpose now

copied from commits 99d5d56d65ee624022f8f9f5577f680f9f386660 and
ccb7870314db6fbf1b9104606888ba67ab535a32 from different branch
and even improved on them (no dict() necessary in print_json args

--> fixed 2 logs from outside of error handlers and
    2 instances were trace is only wanted at debug level