Django 1.9 Exception: no `_choices` attribute about django-timezone-field HOT 4 CLOSED

Thanks. It's probably a historical reason?

At work (where we're using this app, and it's my primary use case) we just upgraded to django 1.7. So I'm going to drop 1.6 support and work on adding 1.9 support as soon as I can. Would love to get time this weekend but I don't think that's going to happen.

from django-timezone-field.

Thanks for the early bug, when 1.9 alpha is released let's see if this is still happening. Looks like that currently scheduled for end of September.

from django-timezone-field.

The error is still occurring with the alpha release. I've managed to track it down to this change: django/django@80e3444

Is there a reason to not simply use self.choices? Or does this break in pre-1.9?

from django-timezone-field.

Fixed on develop, will be in the next release.

from django-timezone-field.