[
http://dataflow-jira.bodleian.ox.ac.uk/jira/browse/DATAFLOW-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10500#comment-10500 ]
Bhavana Ananda commented on DATAFLOW-359:
-----------------------------------------
Just to clarify... according to the Python docs, logging.config.fileConfig by default disables all other configured loggers at the point it's called. As it appears in a module top level, we have no control over if and when it's called.
When used as a library, I think it may be more appropriate that sword client uses a configuration created by a calling program rather than creating it's own... but I find the Python logging system confuses the hell out or me, so there may well be some good reason for doing it the way you do. But we do need to figure out how to play nicely together.
#g
--
> SWORD logging disables global logging
> -------------------------------------
>
> Key: DATAFLOW-359
> URL:
http://dataflow-jira.bodleian.ox.ac.uk/jira/browse/DATAFLOW-359
> Project: DataFlow
> Issue Type: Bug
> Components: DataStage
> Affects Versions: 0.3-rc2
> Reporter: Bhavana Ananda
> Assignee: Richard Jones
> Labels: sword
>
> Having disabled the logging in the
> sword2/sword2_logging.py (full path in my local: /usr/local/lib/python2.7/dist-packages/sword2-0.1-py2.7.egg/sword2/sword2_logging.py) datastage is able to produce its own logging.
> The last line in the file that was disabled was :
> #logging.config.fileConfig(SWORD2_LOGGING_CONFIG)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://dataflow-jira.bodleian.ox.ac.uk/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira