libo26 / feedparser

Automatically exported from code.google.com/p/feedparser
Other
0 stars 0 forks source link

<itunes:summary> and <description> are not distinguishably stored #269

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.
>>> import feedparser
>>> d = feedparser.parse('http://feeds.feedburner.com/linuxoutlaws-ogg')
>>> d.entries[0].content[0]
(snip: stripped html)
>>> d.entries[0].summary
(snip: html)

What is the expected output?

html content in d.entries[0].content[0]

What do you see instead?

the stripped text of the shownotes

What version of the product are you using? On what operating system?

feedparser 5.0.1 & 4.1

Please provide any additional information below.

Found this when using gPodder.
It used to work very well.

Original issue reported on code.google.com by neri...@wanadoo.fr on 20 Apr 2011 at 7:23

GoogleCodeExporter commented 9 years ago
feedparser is putting <itunes:summary> in `content[0]` and <description> in 
`summary`. I'm planning on making itunes support optional so that developers 
such as the gPodder authors can more easily do what they want with itunes 
elements.

Original comment by kurtmckee on 22 Apr 2011 at 7:59

GoogleCodeExporter commented 9 years ago
OK, I had missed this itunes:summary thing !
Would you recommend using the summary instead of content[0] for show notes, 
then ?
Thanks,

Original comment by neri...@wanadoo.fr on 23 Apr 2011 at 7:45

GoogleCodeExporter commented 9 years ago
It will depend on the context your application will use it in; I don't think 
there's a single correct recommendation.

Original comment by kurtmckee on 24 Apr 2011 at 7:31

GoogleCodeExporter commented 9 years ago
After thinking about it, I don't think that there's going to be a single 
correct answer for this that will work for everyone, particularly since 
different feeds use the elements differently, and different feed consumers will 
want to use HTML versus plain text. I'm not going to change the current 
behavior, but I still intend to work on making feedparser easier to extend.

Original comment by kurtmckee on 16 Sep 2011 at 2:32