jason0x43

And now I've actually processed the rest of your post. It apparently takes several passes for me to actually read something. /sigh
Anyway, the problem was that I hadn't tested the workflow with Python 2.6, which is what Snow Leopard comes with. I fixed a few incompatibilities, so it should work now.

Note: This workflow is no longer maintained.
 
This is a really simple workflow that performs unit conversions. Conversion commands look like:
 
    u {value} {in units} > {out units}
 
You can include a space after the u keyword, but it's not required. Units can generally be abbreviated or not, as long as the input is unambiguous. Here are some valid commands:
u 5km > miles u 5km > mi u5km>mi You can also do unit math (again, spaces are generally optional):
u 1cm * 1in u 1in^2 / 2mm^2 u1cm+2.5in-3mm>ft Just remember that units matter. You won't get any output if you try to do something like 1cm * 1in > in, because multiplying two lengths gives an area (like in^2).
 
The calculator is called as you type, so it'll give you an answer whenever you type a query it can process. Actioning the result will copy the value (just the number) to the clipboard. That's it!
 
Well, there are also a couple options you can configure. You can open the configuration file with the command u>. The options are:
"separator" - what separator to use between the input value and output units "precision" - how many decimal digits to include in the output (set to null for unlimited)  
More info and source is available here.
 
 
Download
 
 
Update 2014/05/22:
 
You can now use a space between a number and its units (e.g., "5 km" in addition to "5km").
 
Update 2014/02/06:
 
Unit math is back!
 
Update 2013/12/07:
 
Add output precision option (see above)
 
Update 2013/12/01 (again):
 
Bug fix
 
Update 2013/12/01:
 
Added support for using "space" as the unit separator, so you can do queries like "1mile km".
 
Update 2013/11/30:
 
Added Euros to the currency list. I also added a couple extra commands, accessible with the 'u>' command,
 
Update 2013/11/29:
 
Currency conversion is back.
 
Update 2013/11/25:
 
At last, I pushed out an update that should have this back up and running. It's using a local library now, so it's faster and not subject to the whims of Google. Sorry it took so long.
 
Update 2013/11/5:
 
Google shutdown the API this workflow was using on November 1, so it's broken until I switch it to something else. Sorry about that. I'll have it back up and running in a day or two.
 
Update 2013/10/11:
 
Bugfix
 
Update 2013/8/14:
 
It should now work with Snow Leopard (Python 2.6).
 
Update 2013/8/13:
 
Now with Alleyoop support!

Note: This workflow is no longer maintained.
 
This is a really simple workflow that performs unit conversions. Conversion commands look like:
 
    u {value} {in units} > {out units}
 
You can include a space after the u keyword, but it's not required. Units can generally be abbreviated or not, as long as the input is unambiguous. Here are some valid commands:
u 5km > miles u 5km > mi u5km>mi You can also do unit math (again, spaces are generally optional):
u 1cm * 1in u 1in^2 / 2mm^2 u1cm+2.5in-3mm>ft Just remember that units matter. You won't get any output if you try to do something like 1cm * 1in > in, because multiplying two lengths gives an area (like in^2).
 
The calculator is called as you type, so it'll give you an answer whenever you type a query it can process. Actioning the result will copy the value (just the number) to the clipboard. That's it!
 
Well, there are also a couple options you can configure. You can open the configuration file with the command u>. The options are:
"separator" - what separator to use between the input value and output units "precision" - how many decimal digits to include in the output (set to null for unlimited)  
More info and source is available here.
 
 
Download
 
 
Update 2014/05/22:
 
You can now use a space between a number and its units (e.g., "5 km" in addition to "5km").
 
Update 2014/02/06:
 
Unit math is back!
 
Update 2013/12/07:
 
Add output precision option (see above)
 
Update 2013/12/01 (again):
 
Bug fix
 
Update 2013/12/01:
 
Added support for using "space" as the unit separator, so you can do queries like "1mile km".
 
Update 2013/11/30:
 
Added Euros to the currency list. I also added a couple extra commands, accessible with the 'u>' command,
 
Update 2013/11/29:
 
Currency conversion is back.
 
Update 2013/11/25:
 
At last, I pushed out an update that should have this back up and running. It's using a local library now, so it's faster and not subject to the whims of Google. Sorry it took so long.
 
Update 2013/11/5:
 
Google shutdown the API this workflow was using on November 1, so it's broken until I switch it to something else. Sorry about that. I'll have it back up and running in a day or two.
 
Update 2013/10/11:
 
Bugfix
 
Update 2013/8/14:
 
It should now work with Snow Leopard (Python 2.6).
 
Update 2013/8/13:
 
Now with Alleyoop support!

I wrote a weather forecaster workflow that displays forecasts from Dark Sky or the Weather Underground. This is actually the second iteration; my first was loosely based on David Ferguson's weather workflow, but written in Python. This version is a complete rewrite in Go.
 
The source, along with installation and setup instructions, is available at it at https://github.com/jason0x43/alfred-weather.The most current release can be found at https://github.com/jason0x43/alfred-weather/releases.
 
Version history:
 
2016-12-18: 1.0.0
2017-05-03: 1.3.0
2018-11-08: 1.5.0
2020-05-03: 1.6.0

Pixelmator theme:
 
http://cl.ly/0w3A1N3D3g3D  

 
I love Pixelmator.   
 

Ok, I see the problem, Your service is defined as Weather Underground, but you only have a key for forecast.io. I'm not entirely sure how it got into that state, but you should be able to fix it by running the "wset service" command again.
 
I've posted an updated version of the code that deals with this situation (by asking you to re-specify your service if the service key is missing).

I wrote a weather forecaster workflow that displays forecasts from Dark Sky or the Weather Underground. This is actually the second iteration; my first was loosely based on David Ferguson's weather workflow, but written in Python. This version is a complete rewrite in Go.
 
The source, along with installation and setup instructions, is available at it at https://github.com/jason0x43/alfred-weather.The most current release can be found at https://github.com/jason0x43/alfred-weather/releases.
 
Version history:
 
2016-12-18: 1.0.0
2017-05-03: 1.3.0
2018-11-08: 1.5.0
2020-05-03: 1.6.0

I wrote a weather forecaster workflow that displays forecasts from Dark Sky or the Weather Underground. This is actually the second iteration; my first was loosely based on David Ferguson's weather workflow, but written in Python. This version is a complete rewrite in Go.
 
The source, along with installation and setup instructions, is available at it at https://github.com/jason0x43/alfred-weather.The most current release can be found at https://github.com/jason0x43/alfred-weather/releases.
 
Version history:
 
2016-12-18: 1.0.0
2017-05-03: 1.3.0
2018-11-08: 1.5.0
2020-05-03: 1.6.0

Note: This workflow is no longer maintained.
 
This is a really simple workflow that performs unit conversions. Conversion commands look like:
 
    u {value} {in units} > {out units}
 
You can include a space after the u keyword, but it's not required. Units can generally be abbreviated or not, as long as the input is unambiguous. Here are some valid commands:
u 5km > miles u 5km > mi u5km>mi You can also do unit math (again, spaces are generally optional):
u 1cm * 1in u 1in^2 / 2mm^2 u1cm+2.5in-3mm>ft Just remember that units matter. You won't get any output if you try to do something like 1cm * 1in > in, because multiplying two lengths gives an area (like in^2).
 
The calculator is called as you type, so it'll give you an answer whenever you type a query it can process. Actioning the result will copy the value (just the number) to the clipboard. That's it!
 
Well, there are also a couple options you can configure. You can open the configuration file with the command u>. The options are:
"separator" - what separator to use between the input value and output units "precision" - how many decimal digits to include in the output (set to null for unlimited)  
More info and source is available here.
 
 
Download
 
 
Update 2014/05/22:
 
You can now use a space between a number and its units (e.g., "5 km" in addition to "5km").
 
Update 2014/02/06:
 
Unit math is back!
 
Update 2013/12/07:
 
Add output precision option (see above)
 
Update 2013/12/01 (again):
 
Bug fix
 
Update 2013/12/01:
 
Added support for using "space" as the unit separator, so you can do queries like "1mile km".
 
Update 2013/11/30:
 
Added Euros to the currency list. I also added a couple extra commands, accessible with the 'u>' command,
 
Update 2013/11/29:
 
Currency conversion is back.
 
Update 2013/11/25:
 
At last, I pushed out an update that should have this back up and running. It's using a local library now, so it's faster and not subject to the whims of Google. Sorry it took so long.
 
Update 2013/11/5:
 
Google shutdown the API this workflow was using on November 1, so it's broken until I switch it to something else. Sorry about that. I'll have it back up and running in a day or two.
 
Update 2013/10/11:
 
Bugfix
 
Update 2013/8/14:
 
It should now work with Snow Leopard (Python 2.6).
 
Update 2013/8/13:
 
Now with Alleyoop support!

Note: This workflow is no longer maintained.
 
This is a really simple workflow that performs unit conversions. Conversion commands look like:
 
    u {value} {in units} > {out units}
 
You can include a space after the u keyword, but it's not required. Units can generally be abbreviated or not, as long as the input is unambiguous. Here are some valid commands:
u 5km > miles u 5km > mi u5km>mi You can also do unit math (again, spaces are generally optional):
u 1cm * 1in u 1in^2 / 2mm^2 u1cm+2.5in-3mm>ft Just remember that units matter. You won't get any output if you try to do something like 1cm * 1in > in, because multiplying two lengths gives an area (like in^2).
 
The calculator is called as you type, so it'll give you an answer whenever you type a query it can process. Actioning the result will copy the value (just the number) to the clipboard. That's it!
 
Well, there are also a couple options you can configure. You can open the configuration file with the command u>. The options are:
"separator" - what separator to use between the input value and output units "precision" - how many decimal digits to include in the output (set to null for unlimited)  
More info and source is available here.
 
 
Download
 
 
Update 2014/05/22:
 
You can now use a space between a number and its units (e.g., "5 km" in addition to "5km").
 
Update 2014/02/06:
 
Unit math is back!
 
Update 2013/12/07:
 
Add output precision option (see above)
 
Update 2013/12/01 (again):
 
Bug fix
 
Update 2013/12/01:
 
Added support for using "space" as the unit separator, so you can do queries like "1mile km".
 
Update 2013/11/30:
 
Added Euros to the currency list. I also added a couple extra commands, accessible with the 'u>' command,
 
Update 2013/11/29:
 
Currency conversion is back.
 
Update 2013/11/25:
 
At last, I pushed out an update that should have this back up and running. It's using a local library now, so it's faster and not subject to the whims of Google. Sorry it took so long.
 
Update 2013/11/5:
 
Google shutdown the API this workflow was using on November 1, so it's broken until I switch it to something else. Sorry about that. I'll have it back up and running in a day or two.
 
Update 2013/10/11:
 
Bugfix
 
Update 2013/8/14:
 
It should now work with Snow Leopard (Python 2.6).
 
Update 2013/8/13:
 
Now with Alleyoop support!

Variety is the spice of life.

I wrote a weather forecaster workflow that displays forecasts from Dark Sky or the Weather Underground. This is actually the second iteration; my first was loosely based on David Ferguson's weather workflow, but written in Python. This version is a complete rewrite in Go.
 
The source, along with installation and setup instructions, is available at it at https://github.com/jason0x43/alfred-weather.The most current release can be found at https://github.com/jason0x43/alfred-weather/releases.
 
Version history:
 
2016-12-18: 1.0.0
2017-05-03: 1.3.0
2018-11-08: 1.5.0
2020-05-03: 1.6.0