Modify logging in prior engine

[tramsauer]

We have included a prior engine specific logging..however this may cause trouble in the auto-documentation process..see #40

I read that

Modules, that is, libraries intended to be used by other programs, should only emit log messages as a best practice. They should never configure how log messages are handled. That is the responsibility of the application that imports and uses the modules.

Is a MULTIPLY application-wide logger (possibly based in multiply-core) envisaged? And if so should we just instatiate loggers via

import logging

log = logging.getLogger(__name__)

def do_something():
    log.debug("Doing something!")

[TonioF]

We need to define how to monitor the state of a component's task. This could come together with a logger, but this has not been conceived yet.

For now, every component does its own logging and doing it as you described above is perfectly fine (and done by several components).