title: Django default=timezone.now() saves records using "old" time
body: <p>This issue has been occurring on and off for a few weeks now, and it's unlike any that has come up with my project. </p>
  
  <p>Two of the models that are used have a timestamp field, which is by default set to <code>timezone.now()</code>. </p>
  
  <p>This is the sequence that raises error flags:</p>
  
  <hr>
  
  <ul>
  <li><p>Model one is created at time 7:30 PM</p></li>
  <li><p>Model two is created at time 10:00 PM, but in the 
     MySQL database it's stored as 7:30 PM! </p></li>
  </ul>
  
  <p>Every model that is created 
      has its time stamp saved under 7:30 PM, not the actual time, until a certain
      duration passes. Then a new time is set and all the following models
      have that new time... Bizzare</p>
  
  <hr>
  
  <p>Some extra details which may help in discovering the issue:</p>
  
  <p>I have a bunch of methods that I use to strip my timezones of their <code>tzinfo</code>'s and replace them with UTC. </p>
  
  <p>This is because I'm doing a <code>timezone.now() - creationTime</code> calculation to create a: "model was posted this long ago" feature
  in the project. However, this really should not be the cause of the problem.</p>
  
  <p>I don't think using <code>datetime.datetime.now()</code> will make any difference either.</p>
  
  <p>Anyway, thanks for the help!</p>