simple bug fix in Session.py >> DbmSesssion >> dbm_cleanup for conflicting use of dbm variable#49
Merged
grisha merged 3 commits intogrisha:masterfrom May 6, 2016
Merged
Conversation
…ised with traceback correctly
…logging of the apache error log with deprecation warnings
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
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.
The variable "dbm" was used for both the name of dbm file and the dbm module in Session.py >> DbmSesssion >> dbm_cleanup. The simple fix was to use a new variable "filename" for the name of the dbm file.