Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make model DateTime fields timezone aware. #153

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

martey
Copy link
Contributor

@martey martey commented Dec 25, 2016

Make all Datetime fields in models using datetime.datetime.now switch
to the timezone-aware django.utils.timezone.now.

Fields changed include:

  • reviews.models.Comments.commented_at
  • reviews.models.LatestVote.submitted_at
  • reviews.models.ProposalMessage.submitted_at
  • reviews.models.ResultNotification.timestamp
  • reviews.models.Review.submitted_at
  • reviews.models.ReviewAssignment.assigned_at
  • schedule.models.SessionRole.submitted
  • speakers.models.Speaker.created
  • sponsorship.models.Sponsor.added
  • teams.models.Team.created

Make all Datetime fields in models using `datetime.datetime.now` switch
to the timezone-aware `django.utils.timezone.now`.

Fields changed include:

  - reviews.models.Comments.commented_at
  - reviews.models.LatestVote.submitted_at
  - reviews.models.ProposalMessage.submitted_at
  - reviews.models.ResultNotification.timestamp
  - reviews.models.Review.submitted_at
  - reviews.models.ReviewAssignment.assigned_at
  - schedule.models.SessionRole.submitted
  - speakers.models.Speaker.created
  - sponsorship.models.Sponsor.added
  - teams.models.Team.created
@martey martey force-pushed the timezone-aware-fields branch from 991a3d8 to 83b8e2a Compare January 8, 2017 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant