Support Timezone in DateTimeField for the Meetup model

Open
#111 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
django, python
Domain
backend, databases

Research direction

Locate the Meetup model and its time DateTimeField, then trace how the field receives the naive datetimes shown in the warning. Reproduce the warning with timezone support enabled and confirm that the Meetup time is handled without that warning.

Written by the indexing model from the issue text.

Description

2021-03-23T12:31:11.405922+00:00 app[web.1]: /app/.heroku/python/lib/python3.9/site-packages/django/db/models/fields/__init__.py:1367: RuntimeWarning: DateTimeField Meetup.time received a naive datetime (2021-03-23 12:31:11.405466) while time zone support is active.
2021-03-23T12:31:11.405933+00:00 app[web.1]: warnings.warn("DateTimeField %s received a naive datetime (%s)"
2021-03-23T12:31:11.406411+00:00 app[web.1]: /app/.heroku/python/lib/python3.9/site-packages/django/db/models/fields/__init__.py:1367: RuntimeWarning: DateTimeField Meetup.time received a naive datetime (2021-06-23 12:31:11.405466) while time zone support is active.
2021-03-23T12:31:11.406413+00:00 app[web.1]: warnings.warn("DateTimeField %s received a naive datetime (%s)"
Dominant language
Python
Stars
17
Forks
27
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PythonIreland/website

All issues in PythonIreland/website

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.