Add logging and expose debug output settings in plugin configuration #50
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
PamelaM
changed the title
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.
Many of the issues that have been created are configuration and environment related, so they have been difficult to debug and identify.
This PR exposes the 2 existing debugging flags
SHOW_TRACINGandSHOW_PARSINGto the config file options (as per coverage.py documentation). It also adds 2 more:SHOW_STARTUPandLOG_FILE.SHOW_STARTUPenables extra logging in code that's called during startup, as well as logging the python and django versions.LOG_FILE(calledlog_file_pathin the config option) is an optional argument allowing the user to capture all django_coverage_plugin logging to one file, which can be included or requested when tracking down issues.