xpe VS wttr.in

xpe - a commandline xpath parser. xpaths are better than css queries for getting at specific html elements in the DOM. Compared to other parsers, this one is easier to use, and supports html.

I use the heck out of xpe. It's a super simple command-line xpath parser using lxml in python.

If you like xmllint, you might like xpe. It's more user-friendly.

xpe - a commandline xpath parser. I made this after trying to use xpaths for web automation in bash, and not finding anything that worked.

For commandline xpath parsing for simple commandline web automation, xpe is pretty handy. It's a real simple python script, but it scratches that itch, and it's only a pip install away.

wttr.in is unfortunately not accurate in many cities in the world, check their github issues

The difference with weafetch is that it has its own config file which can just be configured and not touched anymore. When using wttr.in with curl, any custom changes you want to get from the output will need to be typed in everytime.

What about https://wttr.in/ ?

The source of the data that are presented: https://github.com/chubin/wttr.in

I don't recommend using wttr.io at all, their current provider shows inaccurate information for many cities, including Berlin. (source)

Oups the last link was incorrect it should have been https://github.com/chubin/wttr.in. I pull the info and store it in a txt file then I reference with cat or sed. That way it's super quick.

See https://github.com/chubin/wttr.in