ISO8601 datetime parsing fails when milliseconds are included in feed

[GoogleCodeExporter]

Atom Feeds containing milliseconds in datetime fields fail _iso8601_re parsing

Adding optional millisecond section to regex appears to fix it.  

Seen these time stamps in Blogger atom feeds.

1863d1862
<     + r'(.(?P<millisecond>\d{3}))?'    # Patched for optional milliseconds

Original issue reported on code.google.com by djohns...@gmail.com on 23 Dec 2010 at 5:29

• Merged into: #50

[GoogleCodeExporter]

Could you add a testcase. Ideally this would be a minimal feed that 
demonstrates the problem. Something like this: 
http://code.google.com/p/feedparser/source/browse/trunk/feedparser/tests/wellfor
med/date/feed_updated_frac_secs.xml?r=348 would be a good example.

Original comment by adewale on 24 Dec 2010 at 11:49

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

@Adewale: This is a duplicate of issue 50. I'm attaching a minimal feed 
generated by Blogger that svn trunk can parse fine.

@djohnston: This is fixed in the current feedparser code, so while we're 
gearing up for a new release in the next two or three weeks, you can download 
the latest code at:

  https://feedparser.googlecode.com/svn/trunk/feedparser/feedparser.py

Please be aware that the code is currently in a state of flux, so if you run 
into any problems with the current version, please see if it's a known issue 
and report it if there's not an open report about it -- we really appreciate 
the assistance!

Original comment by kurtmckee on 24 Dec 2010 at 6:20

• Added labels: ****
• Removed labels: ****

Attachments:

• demonstrate_issue_243.xml

[GoogleCodeExporter]

Original comment by adewale on 25 Dec 2010 at 7:40

• Changed state: Duplicate
• Added labels: ****
• Removed labels: ****