Hi Felix, On Mon, Feb 13, 2012 at 08:57:26PM -0800, Felix Rabinovich wrote: > On 2/12/2012 2:47 AM, Thomas Perl wrote: > >On Sat, Feb 11, 2012 at 10:03:37AM -0800, Ilona Rabinovich wrote: > >>I use command-line version (gpo) on my linux (Fedora 16) server. As > >>a side note, it seems to be the only podcast client that stores the > >>metadata in well-designed database and allows me to read this and > >>use on a webpage. Very nicely done - thank you! > >I'm glad you find it useful. Is that webpage some private pet project or > >is it available somewhere? I'd be interested to have a look how you use > >it - also it might be interesting for the gPodder Web UI. > It is internal tiny front end to gPodder with 2 users (me and my > wife). the source code is here: http://pastebin.com/xZRe16uV . > Nothing special - the PHP part took me less than an hour to write. > Main thing was to figure out how gPodder database works. Looks good - if you want, you can submit it to the bug tracker and I can put it into the "tools/" folder in the source code repository for an example on how to use the gPodder database from another language? > >>So, two related problems on one particular feed - > >>http://radio.nationalreview.com/radioderb/radioderb.xml > >> > >>First, for some reason, gpo doesn't get pubDate field. It looks to > >>me the same way, as it does on other feeds, where it comes across > >>fine, for example, > >> > >><pubDate>Fri, 10 Feb, 2012 09:00:00 EST</pubDate> > >After some trial and error (one can use feedparser._parse_date() to try > >parsing arbitrary strings) I found out that the problem is the comma > >after the month. Removing it lets feedparser get the correct date. > > > >I'ved filed a bug report at the feedparser issue tracker, please > >subscribe there if you want to be informed about updates: > > > > http://code.google.com/p/feedparser/issues/detail?id=327 > > > >Anyway, I used your mail as an excuse to add a workaround to gPodder's > >code and also change the method of getting the pubDate slightly, see: > > > > http://gpodder.org/commit/ee2a5b7e > > > >The fix will be incorporated into the next gPodder version - if > >feedparser fixes this issue and releases a new version, this fix will be > >available to you even if you don't upgrade gPodder (it's a feedparser > >issue or rather, it's an issue in the RSS feed that feedparser could > >work around). > It looks like thanks to your ("our") uncanny analysis feedparser > update is coming soon. Not sure I understand your point about > getting feedparser without upgrading. Are you including feedparser > library from the web (the way people include jquery from Google or > Microsoft CDN)? So, when feedparser guys post their update, your > code will automagically pull the latest? Not that it matters too > much - I don't have a problem with updating gpodder if necessary... No, it merely "depends" on feedparser, which means that for Linux distributions, they will make sure that the "feedparser" package is installed, and if a new feedparser version comes in, it will be updated. For the Windows package, we do bundle feedparser (and mygpoclient) with the gPodder build, so in this case, I need to include a new version of feedparser in the new Windows build. HTH :) Thomas