[Slackbuilds-users] CurseTheWeather maintainer's email and runtime problems
pc_warner at yahoo.com
Fri Oct 10 21:13:12 UTC 2008
I got a little impatient waiting for the patch so I went ahead and made my own :) . Please add the attached patch to the SlackBuild.
As it turns out I only had to change one character in weatherfeed.py to make it work. It sounds like weather.com added a couple comment tags to their feed and that was getting parsed instead of the real data under the weather tag.
Here's the concise thought process for those interested in knowing how I came to this conclusion...
I knew the problem was that the feed changed so I first opened up a current feed to take a look at it.
Here is an example: http://tinyurl.com/4afuph
Running weatherfeed.py by itself showed that the first error appeared when it tried to access data (line 65).
So, I put a print statement to look at the main node name (line 55).
This returned "#comment", but childNodes returns "weather", which is what we want.
--- On Tue, 9/9/08, Martin Lefebvre <dadexter at sekurity.com> wrote:
> From: Martin Lefebvre <dadexter at sekurity.com>
> Subject: Re: [Slackbuilds-users] CurseTheWeather maintainer's email and runtime problems
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Date: Tuesday, September 9, 2008, 9:55 AM
> > The last time I wrote to Martin (for another script) he
> told me in the
> > reply
> > "I'm not part of the SBo project
> > So I think we can assume that all his scripts are
> > Mauro
> most of them are... I have been too busy with work and
> other things to
> take care of them... but CurseTheWeather kinda crapped out
> on me as well,
> which kinda pi**ed me off, so I'll redo my slackbuild
> and send it in when
> it's done.
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives -
> FAQ - http://slackbuilds.org/faq/
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: not available
More information about the SlackBuilds-users