NonExistentTimeError thrown during DST transition about django-timezone-field HOT 4 CLOSED

Ahh, I see what's going on. Thanks @babu-upcomer for the link and more detailed explanation.

Yeah I think for anyone using this field and using the kwarg choices_display='WITH_GMT_OFFSET' they probably got this error during the recent north america DST transition.

It looks like Europe will be undergoing a DST transition in a few weeks, I will plan to get this bug fixed and an update pushed to pypi before then.

from django-timezone-field.

Yeah, under the hood this field uses pytz to get metadata about timezones. If pytz doesn't recognize a string as a valid timezone, it will throw one of those NonExistentTimeError exceptions. So it looks like that's whats happening here: the obsolete timezones are not being recognized by pytz.

If you have to support the obsolete timezones, perhaps just a standard string field with a choices argument might suffice?

from django-timezone-field.

@mfogel Thanks for responding! I think the problem isn't with the obsolete timezones even America/Adak is in pytz.common_timezones. I guess that it can be fixed with any one of the solutions put out here and also this exception from pytz is intentional. is_dst needs to be sent True or False based on the exceptions. Since this blocks the initialization of the models and so the gunicorn workers to crash when they restart, I think this needs to be prioritized. I'm sure that everyone who is using the library in production have had bunch of errors for like an hour in the reported time.

Thanks for the work!
/Babu

from django-timezone-field.

Fix released as part of v4.1.2

from django-timezone-field.