Logging

[aa403]

improved logging support form my other PR and moved onto dedicated branch (interactive login issues need to be handled separately)

[goetzk]

I've just pulled this down to try it out (thanks for working on it by the way). I have a few comments/suggestions:

• I suggest merging your 4 commits in to one - they don't have useful commit messages so there won't be any loss of information
• Remove the logs/ directory from the git repo including its _temp file
• Handling the log directory being missing would seem desirable; I feel it would be even better not to have one and to just write logs.out to something in the calling scripts directory (like -run-.log

Hopefully in the next few days I'll find some time to try it out and see if/how it can be configured to vary the logging output.

[ms5]

I think logging should not be part of the API but of the custom program code. Defining a log destination, format logs, etc is part of the application and differs a lot from system and or application. therefore i suggest to not create a logger inside the api. this can easily be created in the application. events logged with the python logger will still be available in the application logger.

especially what is done in "bf_logging.py" belongs really to the application and not the the api.