title: Django with system timezone setting vs user's individual timezones
body: <p>How well does Django handle the case of different timezones for each user?  Ideally I would like to run the server in the UTC timezone (eg, in settings.py set TIME_ZONE="UTC") so all datetimes were stored in the database as UTC.  Stuff like <a href="https://stackoverflow.com/questions/689831/changing-timezone-on-an-existing-django-project">this</a> scares me which is why I prefer UTC everywhere.</p>
  
  <p>But how hard will it be to store a timezone for each user and still use the standard django datetime formatting and modelform wrappers.  Do I anticipate having to write date handling code everywhere to convert dates into the user's timezone and back to UTC again?</p>
  
  <p>I am still going through the django tutorial but I know how much of a pain it can be to deal with user timezones in some other frameworks that assume system timezone everywhere so I thought I'd ask now.</p>
  
  <p>My research at the moment consisted of searching the django documentation and only finding <a href="http://docs.djangoproject.com/en/dev/ref/settings/#time-zone" rel="nofollow noreferrer">one reference</a> to timezones.</p>
  
  <hr>
  
  <p>Additional: </p>
  
  <ul>
  <li>There are a <a href="http://code.djangoproject.com/ticket/2626" rel="nofollow noreferrer">few bugs submitted</a> concerning Django and timezone handling.</li>
  <li>Babel has <a href="http://svn.edgewall.org/repos/babel/contrib/django/" rel="nofollow noreferrer">some contrib code for django</a> that seems to deal with timezone formatting in locales.</li>
  </ul>