#32366: Update usage of now() & co
-------------------------------------+-------------------------------------
Reporter: Carlton Gibson | Owner: Nick Pope
Type: | Status: closed
Cleanup/optimization |
Component: Utilities | Version: 4.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson <carlton.gibson@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"d06c5b358149c02a62da8a5469264d05f29ac659" d06c5b3]:
{{{
#!CommitTicketReference repository=""
revision="d06c5b358149c02a62da8a5469264d05f29ac659"
Fixed #32366 -- Updated datetime module usage to recommended approach.
- Replaced datetime.utcnow() with datetime.now().
- Replaced datetime.utcfromtimestamp() with datetime.fromtimestamp().
- Replaced datetime.utctimetuple() with datetime.timetuple().
- Replaced calendar.timegm() and datetime.utctimetuple() with
datetime.timestamp().
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32366#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.0e3aa6c3f99c877fb49f462b957e9e24%40djangoproject.com.
