[Django] #33922: New version of pytz is breaking Django 3.2.x

68 views
Skip to first unread message

Django

unread,
Aug 12, 2022, 4:36:42 AM8/12/22
to django-...@googlegroups.com
#33922: New version of pytz is breaking Django 3.2.x
-------------------------------------------+------------------------
Reporter: Denny Biasiolli | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+------------------------
pytz is not explicitly boud to a specific version, so when installing
Django it takes the last one available.
Currently it's taking the 2022.2 version and when launching Django it
gives this error:

```
ModuleNotFoundError: No module named 'tzdata'

(...)

backports.zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with
key Asia/Hanoi'
```

Let me know if you need more info/logs


Related to this pytz issue: https://github.com/stub42/pytz/issues/79

--
Ticket URL: <https://code.djangoproject.com/ticket/33922>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Aug 12, 2022, 4:57:55 AM8/12/22
to django-...@googlegroups.com
#33922: New version of pytz is breaking Django 3.2.x
---------------------------------+--------------------------------------

Reporter: Denny Biasiolli | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution: invalid

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Denny Biasiolli):

* status: new => closed
* resolution: => invalid


Comment:

Actually the problem is not in Django itself, I was creating a new
repository using only Django 3.2 and the problem does not exists.
In my case, the problem seems to be related to this package: django-
timezone-field

--
Ticket URL: <https://code.djangoproject.com/ticket/33922#comment:1>

Django

unread,
Aug 13, 2022, 4:54:51 AM8/13/22
to django-...@googlegroups.com
#33922: New version of pytz is breaking Django 3.2.x
---------------------------------+--------------------------------------
Reporter: Denny Biasiolli | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------

Comment (by Carlton Gibson):

This looks like a duplicate of #33814, related to the move to use
`ZoneInfo`.

Your system likely doesn't have the timezone database installed, so `pip
install tzdata` should resolve it for you.

--
Ticket URL: <https://code.djangoproject.com/ticket/33922#comment:2>

Reply all
Reply to author
Forward
0 new messages