Updated docstring to correctly reflect where 'now' is coming from. #630
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.
Updated docstring to correctly reflect where
now
is coming from in theAutoCreatedField
andAutoLastModifiedField
field models.Problem
Docstring was showing that the
now
function was coming fromdatetime
instead ofdjango.utils.timezone
Solution
Replaced
datetime.now
todjango.utils.timezone.now
in the docstringsCommandments
CHANGES.rst
file to describe the changes, and quote according issue withGH-<issue_number>
.