Enable presubmit pylint in build/android.

build/android/pylib/base/base_test_result_unittest.py

Index: build/android/pylib/base/base_test_result_unittest.py
diff --git a/build/android/pylib/base/base_test_result_unittest.py b/build/android/pylib/base/base_test_result_unittest.py
index f038b31992bdd8bf092c70e9be958b3efbdbeb98..1532563f5e08c19899a6358963bf9c2f0b983e31 100644
--- a/build/android/pylib/base/base_test_result_unittest.py
+++ b/build/android/pylib/base/base_test_result_unittest.py
@@ -6,9 +6,9 @@
 
 import unittest
 
-from base_test_result import BaseTestResult
-from base_test_result import TestRunResults
-from base_test_result import ResultType
+from .base_test_result import BaseTestResult
+from .base_test_result import TestRunResults
+from .base_test_result import ResultType

[frankf, 2014/02/03 18:58:51]

Why is explicit relative import preferred?

Note according to google style guide:

"Do not use relative names in imports. Even if the module is in the same
package, use the full package name. This helps prevent unintentionally importing
a package twice."

Note sure how this plays with pythin unittest, I have a vague recollection that
there was an issue with that. You don't need to do this change in this CL since
it's already big.

[jbudorick, 2014/02/03 19:33:57]

Explicit relative import is preferred because, well, it's explicit. You can tell
that it's a relative import and not an absolute one.

I didn't realize that that was a rule. I can switch to absolute imports.

 
 
 class TestTestRunResults(unittest.TestCase):