Don't hard-code python path.

Don't hard-code python path.

Recently upgraded Macs have Python 2.7 in /usr/local/bin and the
hard-coded path is breaking the compile step.

R=mark@chromium.org
BUG=304948
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=229375

[M-A Ruel, 2013-10-17 16:02:25]

lgtm (but you'll want to upload again)

[commit-bot: I haz the power, 2013-10-17 16:13:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mmoss@chromium.org/27593003/10001

[commit-bot: I haz the power, 2013-10-18 01:49:12]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mmoss@chromium.org/27593003/10001

[commit-bot: I haz the power, 2013-10-18 12:22:10]

Change committed as 229375

[Mark Mentovai, 2013-10-25 20:37:07]

LGTM, but

> Recently upgraded Macs have Python 2.7 in /usr/local/bin and the
> hard-coded path is breaking the compile step.

Huh? Who broke /usr/bin/python? That should always be there and should always
work. Who says /usr/local/bin is even in the PATH? On a fresh OS install,
/usr/bin is the first thing in the PATH, and /usr/local/bin is the last.

[Michael Moss, 2013-10-25 20:39:21]

On 2013/10/25 20:37:07, Mark Mentovai wrote:
> LGTM, but
> 
> > Recently upgraded Macs have Python 2.7 in /usr/local/bin and the
> > hard-coded path is breaking the compile step.
> 
> Huh? Who broke /usr/bin/python? That should always be there and should always

Uh, sysadmins I guess? I assume it's the result of
https://code.google.com/p/chromium/issues/detail?id=279482

> work. Who says /usr/local/bin is even in the PATH? On a fresh OS install,
> /usr/bin is the first thing in the PATH, and /usr/local/bin is the last.