<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>t+1 - Latest Comments in How to load ditz issues into python</title><link>http://tplus1.disqus.com/</link><description></description><atom:link href="http://tplus1.disqus.com/how_to_load_ditz_issues_into_python/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 29 May 2009 18:05:11 -0000</lastBuildDate><item><title>Re: How to load ditz issues into python</title><link>http://blog.tplus1.com/index.php/2009/03/04/how-to-load-ditz-issues-into-python/#comment-10276306</link><description>&lt;p&gt;That trailing Z IS important, I agree.  But I can't fix it -- it's a&lt;br&gt;ruby bug as far as I can tell.&lt;/p&gt;

&lt;p&gt;Thanks for the comment!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Wilson</dc:creator><pubDate>Fri, 29 May 2009 18:05:11 -0000</pubDate></item><item><title>Re: How to load ditz issues into python</title><link>http://blog.tplus1.com/index.php/2009/03/04/how-to-load-ditz-issues-into-python/#comment-10276042</link><description>&lt;p&gt;That trailing Z seems important.Also, python and ruby seem to write out lists differently. Here’s how python dumped a list of lists:&amp;gt;&amp;gt;&amp;gt; print yaml.dump(issue.log_events)&lt;br&gt;- [!!timestamp '2008-09-02 17:47:44.549355', Matthew Wilson , created,&lt;br&gt;  '']- [!!timestamp '2008-09-02 19:18:03.286902', Matthew Wilson , assignedto release 3.5.1 from unassigned, '']&lt;br&gt;- [!!timestamp '2008-09-04 18:27:19.571991', &lt;a href="http://www.thrift-savings-plan.net" rel="nofollow"&gt;thrift savings plan&lt;/a&gt;  Matthew Wilson , unassigned&lt;br&gt;    from release 3.5.1, '']But the same data dumped by ruby looks like:&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">briceachang</dc:creator><pubDate>Fri, 29 May 2009 17:55:10 -0000</pubDate></item><item><title>Re: How to load ditz issues into python</title><link>http://blog.tplus1.com/index.php/2009/03/04/how-to-load-ditz-issues-into-python/#comment-6888743</link><description>&lt;p&gt;Mark -- thanks for the tip.  I can't use safe_dump on a complex object, but default_flow_style=False helps a lot.  Now I need to know how to make my datetime object with a time zone.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Wilson</dc:creator><pubDate>Wed, 04 Mar 2009 22:13:28 -0000</pubDate></item><item><title>Re: How to load ditz issues into python</title><link>http://blog.tplus1.com/index.php/2009/03/04/how-to-load-ditz-issues-into-python/#comment-6880090</link><description>&lt;p&gt;It's the ISO 8601 date format.  The trailing Z indicates the time is in UTC; lack of it doesn't say anything about the timezone.&lt;/p&gt;

&lt;p&gt;I've had a brief brush with YAML.  It has more than one way to express various data structures.  If both your YAML generator and the Ditz YAML parser implement the spec in the same way, this shouldn't cause any problems, in theory.&lt;/p&gt;

&lt;p&gt;YAML tried to be both human-friendly and simpler than XML.  I personally think it failed on both counts.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marius Gedminas</dc:creator><pubDate>Wed, 04 Mar 2009 15:54:37 -0000</pubDate></item><item><title>Re: How to load ditz issues into python</title><link>http://blog.tplus1.com/index.php/2009/03/04/how-to-load-ditz-issues-into-python/#comment-6873208</link><description>&lt;p&gt;You can make the YAML dump much nicer with a few settings..&lt;/p&gt;

&lt;p&gt;Try something like&lt;br&gt;yaml.safe_dump(data, default_flow_style = False, allow_unicode = True)&lt;/p&gt;

&lt;p&gt;its quite a while since I looked at this - but if I remember this makes the output YAML a bit more user friendly (though I didn't  have datetime instances in my dump I believe).&lt;/p&gt;

&lt;p&gt;Good luck.&lt;br&gt;  Mark&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark</dc:creator><pubDate>Wed, 04 Mar 2009 11:47:56 -0000</pubDate></item></channel></rss>
