Workflows with Python do not work

[Chancho]

Any workflow that uses python just doesn't work. I tried reinstalling python (2.7.9), but didn't seem to help. Checked the console to see if any errors were being outputted but didn't look like it. All other workflows work great... anyone experience this or know how to fix it??

 

thanks!

[Andrew]

Any workflow that uses python just doesn't work. I tried reinstalling python (2.7.9), but didn't seem to help. Checked the console to see if any errors were being outputted but didn't look like it. All other workflows work great... anyone experience this or know how to fix it??

 

thanks!

 

Hi there,

 

Are you running Alfred 2.7.1 as this has a small fix relating to Python workflows?

 

cheers,

Andrew

[deanishe]

Hi there,

 

Are you running Alfred 2.7.1 as this has a small fix relating to Python workflows?

 

cheers,

Andrew

 

The 2.7.0 bug that I caused only affects workflows that explicitly use Python's locale library (well, that should be the case…), which vanishingly few do because it does nothing in Alfred (there is no locale).

 

@Chacho: Alfred uses the system Python (at /usr/bin/python) unless another Python is explicitly specified. You can't just "reinstall" the system Python. Any Python you install will end up at /usr/local/bin/python, not /usr/bin/python, where the system Python is installed. Workflow scripts will not run with /usr/local/bin/python unless you explicitly set them to do so: /usr/local/bin isn't on the default (i.e. Alfred's) $PATH.

 

If no Python workflows are working, it's likely that something bad has happened to the /usr/bin/python program. Could you test running some of the workflow scripts (and other scripts) directly with /usr/bin/python? Or just try running /usr/bin/python directly from a terminal.

If there's something wrong with /usr/bin/python, you've screwed up your operating system (in a fairly small way). OS X's recovery/repair mechanisms are the solution in that case.

[Chancho]

Thanks for the prompt replies! Seems I had a bad workflow in combination with work flows that needed to be configured properly... so more of a user error than anything.