The logic for overriding time zones of t_begin and t_end is quite a mess. Consider another approach.

[yarwelp]

Perhaps the DateTimeField type can be subclassed and extended with input of time zone and then we can read the time zone provided to the subclassed DateTimeField and put that in the tz_begin and tz_end fields respectively?

[yarwelp]

Relevant Django documentation:

• https://docs.djangoproject.com/en/1.7/ref/forms/fields/#datetimefield
  • https://docs.djangoproject.com/en/1.7/ref/forms/widgets/#django.forms.DateTimeInput
• https://docs.djangoproject.com/en/1.7/ref/models/fields/#datetimefield

[yarwelp]

Also, this, which I think I saw posted to HN recently though I can't seem to find it using algolia HN search.

Anyway, link: http://momentjs.com/timezone/

[yarwelp]

If it works, it works.