<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Django and time zone-aware date fields</title>
	<atom:link href="http://reliablybroken.com/b/2009/06/django-and-time-zone-aware-date-fields/feed/" rel="self" type="application/rss+xml" />
	<link>http://reliablybroken.com/b/2009/06/django-and-time-zone-aware-date-fields/</link>
	<description>It&#039;s a blog: let&#039;s do funch!</description>
	<lastBuildDate>Fri, 03 Sep 2010 20:44:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: django in june</title>
		<link>http://reliablybroken.com/b/2009/06/django-and-time-zone-aware-date-fields/comment-page-1/#comment-706</link>
		<dc:creator>django in june</dc:creator>
		<pubDate>Sat, 27 Mar 2010 04:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=168#comment-706</guid>
		<description>&lt;p&gt;[...] you ... you want a partial field to work with django newforms and a database entry, let me know, ...Reliably Broken Django and time zone-aware date fieldsDjango and time zone-aware date fields ... This extra method is intended for use in a Django [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] you &#8230; you want a partial field to work with django newforms and a database entry, let me know, &#8230;Reliably Broken Django and time zone-aware date fieldsDjango and time zone-aware date fields &#8230; This extra method is intended for use in a Django [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://reliablybroken.com/b/2009/06/django-and-time-zone-aware-date-fields/comment-page-1/#comment-355</link>
		<dc:creator>david</dc:creator>
		<pubDate>Sat, 01 Aug 2009 21:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=168#comment-355</guid>
		<description>&lt;p&gt;Posted the complete package

http://reliablybroken.com/b/2009/08/django-and-time-zone-aware-date-fields-redux/&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Posted the complete package

<a href="http://reliablybroken.com/b/2009/08/django-and-time-zone-aware-date-fields-redux/" rel="nofollow">http://reliablybroken.com/b/2009/08/django-and-time-zone-aware-date-fields-redux/</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Reliably Broken &#187; Django and time zone-aware date fields (redux)</title>
		<link>http://reliablybroken.com/b/2009/06/django-and-time-zone-aware-date-fields/comment-page-1/#comment-354</link>
		<dc:creator>Reliably Broken &#187; Django and time zone-aware date fields (redux)</dc:creator>
		<pubDate>Sat, 01 Aug 2009 21:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=168#comment-354</guid>
		<description>&lt;p&gt;[...] posted a module for handling time zone-aware datetime objects, but I left out all the hassle of dealing with form input. Here is a more complete python package [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] posted a module for handling time zone-aware datetime objects, but I left out all the hassle of dealing with form input. Here is a more complete python package [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://reliablybroken.com/b/2009/06/django-and-time-zone-aware-date-fields/comment-page-1/#comment-351</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 28 Jul 2009 23:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=168#comment-351</guid>
		<description>&lt;p&gt;No plans to get this into Django. For one thing I haven&#039;t posted the complete package I ended up with that includes a &lt;code&gt;forms.Field&lt;/code&gt; sub-class for processing time zone strings in form inputs.&lt;/p&gt;

&lt;p&gt;Django&#039;s datetime model field and its datetime form field each has its own string parsing routine, which is odd. My approach tries to use a single routine for both cases. If you think you could use it let me know and I&#039;ll put the whole package up here.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>No plans to get this into Django. For one thing I haven&#8217;t posted the complete package I ended up with that includes a <code>forms.Field</code> sub-class for processing time zone strings in form inputs.</p>

<p>Django&#8217;s datetime model field and its datetime form field each has its own string parsing routine, which is odd. My approach tries to use a single routine for both cases. If you think you could use it let me know and I&#8217;ll put the whole package up here.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: guaq</title>
		<link>http://reliablybroken.com/b/2009/06/django-and-time-zone-aware-date-fields/comment-page-1/#comment-350</link>
		<dc:creator>guaq</dc:creator>
		<pubDate>Tue, 28 Jul 2009 18:30:22 +0000</pubDate>
		<guid isPermaLink="false">http://reliablybroken.com/b/?p=168#comment-350</guid>
		<description>&lt;p&gt;This lack of an essential feature is really a pain. One has to write down the actual timezone calculations if there ever is a need to output something in UTC (like RSS feeds). Are you planning to try to get this code into Django?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This lack of an essential feature is really a pain. One has to write down the actual timezone calculations if there ever is a need to output something in UTC (like RSS feeds). Are you planning to try to get this code into Django?</p>]]></content:encoded>
	</item>
</channel>
</rss>
