Code simplifications and fixes #455
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
This resolves a type mismatch risk, where datetime.strftime() is expecting a DATE, not a DATETIME object. This may be IDE error, but it's also simpler to just refer to the specific datetime.now() object's strftime, rather than call in a separate strftime call.
ArtOfCode-
approved these changes
Jan 16, 2017
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.
Code simplification 1: We don't need to use datetime.strftime(datetime.now(), ...) we can just call strftime from datetime.now() itself.
Code fix 2: Undefined variable reference, I don't think we actually reach that currently, but it could error out (and probably should be from GlobalVars)