title: Correctly saved timezone aware datetime object appearing timezone unaware when accessed in Django app
body: <p>In a Django app w/ postgresql backend I maintain, users log in and post comments. Every comment has a timestamp associated to it. </p>
  
  <p>When creating the comment object, I do:</p>
  
  <pre><code>now = datetime.now()
  Comment.objects.create(commenter=self.request.user, when=now, text='text')
  </code></pre>
  
  <p><code>now</code> is timezone aware - i.e. I am UTC +530, and <code>now</code> encodes that information correctly. If I use <code>psql</code> and peek at the entry created in the Comment postgresql table, I see the correct value for the datetime object.</p>
  
  <p>However, if I access this same object from the Django app, and <code>print</code> out its datetime stamp, I see a timezone <strong>unaware</strong> object. I.e. a datetime object that doesn't know I'm at UTC +530.</p>
  
  <p>This is totally messing up my logic. How do I ensure I get the same datetime object in the Django app that's saved in its related postgresql table? It's remarkable that the two outputs are different, I'm probably doing something fundamentally wrong. Help!</p>