#33922 closed Bug (invalid)
New version of pytz is breaking Django 3.2.x
Reported by: | Denny Biasiolli | Owned by: | nobody |
---|---|---|---|
Component: | Uncategorized | Version: | 3.2 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
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
Change History (2)
comment:1 by , 2 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 2 years ago
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.
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