Stop using third_party\python_26 for many tests.

build/android/pylib/chrome_test_server_spawner.py

Index: build/android/pylib/chrome_test_server_spawner.py
diff --git a/build/android/pylib/chrome_test_server_spawner.py b/build/android/pylib/chrome_test_server_spawner.py
index 642e5223eaf6df06575b64f91a25e9e9bf316ac6..c9489899cd0d1a461a5a472b95c8ab728dad819b 100644
--- a/build/android/pylib/chrome_test_server_spawner.py
+++ b/build/android/pylib/chrome_test_server_spawner.py
@@ -25,15 +25,6 @@ import ports
 
 from pylib.forwarder import Forwarder
 
-# Path that are needed to import necessary modules when launching a testserver.

[M-A Ruel, 2013/12/04 21:16:43]

Modifying os.environ as a side-effect of importing a module is not what can be
called "good practices".

It should not be necessary anyway, android is not different from other platforms
with that regard.

[bulach, 2013/12/06 09:56:54]

sorry about the delay, pliard@ would be a better reviewer for this file..
afaict, the problem is that the top-level test harness for android all start in
build/android, and then some specific tests need to start these servers..
I think this is hooked up at a different level for other platforms.

-os.environ['PYTHONPATH'] = os.environ.get('PYTHONPATH', '') + (':%s:%s:%s:%s:%s'
-    % (os.path.join(constants.DIR_SOURCE_ROOT, 'third_party'),
-       os.path.join(constants.DIR_SOURCE_ROOT, 'third_party', 'tlslite'),
-       os.path.join(constants.DIR_SOURCE_ROOT, 'third_party', 'pyftpdlib',
-                    'src'),
-       os.path.join(constants.DIR_SOURCE_ROOT, 'net', 'tools', 'testserver'),
-       os.path.join(constants.DIR_SOURCE_ROOT, 'sync', 'tools', 'testserver')))
-
 
 SERVER_TYPES = {
     'http': '',