Add back module paths from old python_26 configuration.

Add back module paths from old python_26 configuration.

R=maruel@chromium.org
BUG=304949
Committed: 229213

[Michael Moss, 2013-10-17 19:10:22]

This fixes the import failure on bots that aren't using python 2.7.5 yet, e.g.:
http://build.chromium.org/p/chromium/builders/Win/builds/17487/steps/compile/...

[M-A Ruel, 2013-10-17 19:18:53]

I'd prefer to have whatever library needed in
src\third_party\python_26\Lib\site-packages\ in be extracted in a proper
directory that could be included unconditionally. wdyt?

[Michael Moss, 2013-10-17 19:26:21]

On 2013/10/17 19:18:53, M-A Ruel wrote:
> I'd prefer to have whatever library needed in
> src\third_party\python_26\Lib\site-packages\ in be extracted in a proper
> directory that could be included unconditionally. wdyt?

That sounds like a much more invasive change, for what I'm hoping is just a
temporary, transitional workaround.

[M-A Ruel, 2013-10-17 19:31:40]

On 2013/10/17 19:26:21, Michael Moss wrote:
> On 2013/10/17 19:18:53, M-A Ruel wrote:
> > I'd prefer to have whatever library needed in
> > src\third_party\python_26\Lib\site-packages\ in be extracted in a proper
> > directory that could be included unconditionally. wdyt?
> 
> That sounds like a much more invasive change, for what I'm hoping is just a
> temporary, transitional workaround.

The whole reason for importing this directory is so "google" gets in the path.
It is not actually in this directory, it is in src\tools\python\. There's
google.pth that does the import redirection.

So in the end, what you want to include is "%~dp0\..\..\tools\python".

[Michael Moss, 2013-10-17 19:35:31]

On 2013/10/17 19:31:40, M-A Ruel wrote:
> On 2013/10/17 19:26:21, Michael Moss wrote:
> > On 2013/10/17 19:18:53, M-A Ruel wrote:
> > > I'd prefer to have whatever library needed in
> > > src\third_party\python_26\Lib\site-packages\ in be extracted in a proper
> > > directory that could be included unconditionally. wdyt?
> > 
> > That sounds like a much more invasive change, for what I'm hoping is just a
> > temporary, transitional workaround.
> 
> The whole reason for importing this directory is so "google" gets in the path.
> It is not actually in this directory, it is in src\tools\python\. There's
> google.pth that does the import redirection.
> 
> So in the end, what you want to include is "%~dp0\..\..\tools\python".

But this is PATH, not PYTHONPATH. Or are you saying we should just add
PYTHONPATH and leave PATH the way it was?

[M-A Ruel, 2013-10-17 19:41:19]

Yes, at least if it works.

[Michael Moss, 2013-10-17 19:56:20]

On 2013/10/17 19:41:19, M-A Ruel wrote:
> Yes, at least if it works.

Done.

[M-A Ruel, 2013-10-17 20:01:27]

lgtm

[Michael Moss, 2013-10-17 20:27:56]

Committed patchset #3 manually as r229213 (presubmit successful).