Make jogging compatible with django 1.3 by renaming LOGGING to JOGGING #16
Conversation
This file contains hidden or 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
…GGING is still supported for django < 1.3. If there wasn't LOGGING option defined in settings.py then empty JOGGING={} options should be defined there in order to get things work with django 1.3.
Contributor
|
Why would you want to use jogging with Django 1.3 when it has built in logging? If you have a valid reason please re-open. |
Author
|
That's because some efforts are still necessary to make a transition from jogging to new django 1.3 logging. I updated one of my projects from django 1.2 to django 1.3 and all was fine except for jogging breaking the site. The easiest fix was to change the name of 1 option in 'jogging' package. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.