adoption of Python logging mechanism #64
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
@jreadey I would assume that this PR is almost trivial.. since it just applies the default 'standard' Python logging mechanism.. so I would move forward and merge it by myself. Please feel free to revert it if I underestimated its impact! |
giumas
pushed a commit
that referenced
this pull request
Oct 9, 2015
adoption of Python logging mechanism
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implement one of the milestones in #61
At the same time, it does some work toward #46 by putting
from __future__ import absolute_import, division, print_function, unicode_literalsof top of each module as well as by dropping the Py2-styleprint