<?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: Python Date Manipulation</title>
	<atom:link href="http://www.protocolostomy.com/2010/07/06/python-date-manipulation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.protocolostomy.com/2010/07/06/python-date-manipulation/</link>
	<description>Made with only the finest 1's and 0's</description>
	<lastBuildDate>Thu, 26 Jan 2012 21:20:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ben Sizer</title>
		<link>http://www.protocolostomy.com/2010/07/06/python-date-manipulation/comment-page-1/#comment-42663</link>
		<dc:creator>Ben Sizer</dc:creator>
		<pubDate>Wed, 07 Jul 2010 16:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=781#comment-42663</guid>
		<description>I have nothing useful to add except that I agree it&#039;s a bit confusing, that I personally think the modules should be consolidated and improved somewhat, and I raised this point on comp.lang.python almost 7 years ago. :) 

http://groups.google.com/group/comp.lang.python/browse_frm/thread/f1fe5bd5e1f8d8ba/

If nothing else, you might find some of the discussion interesting as it talks about why datetime ended up the way that it did.</description>
		<content:encoded><![CDATA[<p>I have nothing useful to add except that I agree it&#8217;s a bit confusing, that I personally think the modules should be consolidated and improved somewhat, and I raised this point on comp.lang.python almost 7 years ago. <img src='http://www.protocolostomy.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p><a href="http://groups.google.com/group/comp.lang.python/browse_frm/thread/f1fe5bd5e1f8d8ba/" rel="nofollow">http://groups.google.com/group/comp.lang.python/browse_frm/thread/f1fe5bd5e1f8d8ba/</a></p>
<p>If nothing else, you might find some of the discussion interesting as it talks about why datetime ended up the way that it did.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m0j0</title>
		<link>http://www.protocolostomy.com/2010/07/06/python-date-manipulation/comment-page-1/#comment-42636</link>
		<dc:creator>m0j0</dc:creator>
		<pubDate>Wed, 07 Jul 2010 12:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=781#comment-42636</guid>
		<description>The article mentions dateutil, but to reiterate what was said there, I shouldn&#039;t really need to have yet another third-party module to perform these operations. It&#039;s not that they&#039;re not supported per se, it&#039;s that they&#039;re not presented in as straightforward manner as I (and many others I gather) would like.</description>
		<content:encoded><![CDATA[<p>The article mentions dateutil, but to reiterate what was said there, I shouldn&#8217;t really need to have yet another third-party module to perform these operations. It&#8217;s not that they&#8217;re not supported per se, it&#8217;s that they&#8217;re not presented in as straightforward manner as I (and many others I gather) would like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence</title>
		<link>http://www.protocolostomy.com/2010/07/06/python-date-manipulation/comment-page-1/#comment-42634</link>
		<dc:creator>Lawrence</dc:creator>
		<pubDate>Wed, 07 Jul 2010 12:38:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=781#comment-42634</guid>
		<description>Very much want to confirm the previous suggestion to look at http://labix.org/python-dateutil
for a good tested utility.</description>
		<content:encoded><![CDATA[<p>Very much want to confirm the previous suggestion to look at <a href="http://labix.org/python-dateutil" rel="nofollow">http://labix.org/python-dateutil</a><br />
for a good tested utility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric G</title>
		<link>http://www.protocolostomy.com/2010/07/06/python-date-manipulation/comment-page-1/#comment-42613</link>
		<dc:creator>Eric G</dc:creator>
		<pubDate>Wed, 07 Jul 2010 09:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=781#comment-42613</guid>
		<description>The two main issues I have with python date and time are fairly basic.

1) With 3 separate modules, as much as they share a common interface, there&#039;s enough difference to cause some annoyance at times. Not to mention that often enough you will need to import more than one to get the job done any ways. I would prefer them to be concentrated into one module or even better one object to reduce API confusion and otherwise unnecessary statements to combine them.

2) strptime. I&#039;ll admit it&#039;s better than nothing, but invariably I find myself trying to account for &quot;/&quot; vs &quot;-&quot; in dates as well as datetimes vs dates vs times with a series of try/excepts (which I really think look &quot;ugly&quot; but unavoidable at times). I know I could filter all that in the interface but sometimes you&#039;re dealing with raw input that you can&#039;t control. Ideally it should recognize the most common date and time formats without intervention or ambiguity. I know that&#039;s a tall order but that is what would make things easier for me and possibly allow free form date and time entries for users.

Maybe my ideas are off base and completely wrong. Just my two cents.</description>
		<content:encoded><![CDATA[<p>The two main issues I have with python date and time are fairly basic.</p>
<p>1) With 3 separate modules, as much as they share a common interface, there&#8217;s enough difference to cause some annoyance at times. Not to mention that often enough you will need to import more than one to get the job done any ways. I would prefer them to be concentrated into one module or even better one object to reduce API confusion and otherwise unnecessary statements to combine them.</p>
<p>2) strptime. I&#8217;ll admit it&#8217;s better than nothing, but invariably I find myself trying to account for &#8220;/&#8221; vs &#8220;-&#8221; in dates as well as datetimes vs dates vs times with a series of try/excepts (which I really think look &#8220;ugly&#8221; but unavoidable at times). I know I could filter all that in the interface but sometimes you&#8217;re dealing with raw input that you can&#8217;t control. Ideally it should recognize the most common date and time formats without intervention or ambiguity. I know that&#8217;s a tall order but that is what would make things easier for me and possibly allow free form date and time entries for users.</p>
<p>Maybe my ideas are off base and completely wrong. Just my two cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: itsadok</title>
		<link>http://www.protocolostomy.com/2010/07/06/python-date-manipulation/comment-page-1/#comment-42590</link>
		<dc:creator>itsadok</dc:creator>
		<pubDate>Wed, 07 Jul 2010 05:51:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=781#comment-42590</guid>
		<description>The article at http://seehuhn.de/pages/pdate has some good advice about using dates in python. Namely, stick to the datetime module and convert everything else into a datetime object as soon as possible.

Still, timezone is not really handled easily with python. I&#039;m still waiting for somebody to port joda-time or JSR-310 to python.</description>
		<content:encoded><![CDATA[<p>The article at <a href="http://seehuhn.de/pages/pdate" rel="nofollow">http://seehuhn.de/pages/pdate</a> has some good advice about using dates in python. Namely, stick to the datetime module and convert everything else into a datetime object as soon as possible.</p>
<p>Still, timezone is not really handled easily with python. I&#8217;m still waiting for somebody to port joda-time or JSR-310 to python.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

