autotest: Update CODING_STYLE to have imports one per line
This has long been the standard practice within autotest maintainers
on ChromeOS and is more consistent with every other style guide.
BUG=None
TEST=None
Change-Id: Iba57c06523526e5bd401a82fb0373762a80256cd
Reviewed-on: https://chromium-review.googlesource.com/233620
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
diff --git a/CODING_STYLE b/CODING_STYLE
index 44ec4bf..9df3294 100644
--- a/CODING_STYLE
+++ b/CODING_STYLE
@@ -69,7 +69,7 @@
Within one of these three sections, all module imports using the from
keyword should appear after regular imports.
-Modules should be lumped together on the same line.
+Each module should be imported on its own line.
Wildcard imports (from x import *) should be avoided if possible.
Classes should not be imported from modules, but modules may be imported
from packages, i.e.:
@@ -78,12 +78,21 @@
from common_lib.error import AutoservError
For example:
-import os, pickle, random, re, select, shutil, signal, StringIO, subprocess
-import sys, time, urllib, urlparse
+import os
+import pickle
+import random
+import re
+import select
+import shutil
+import signal
+import subprocess
+
import common # Magic autotest_lib module and sys.path setup code.
import MySQLdb # After common so that we check our site-packages first.
+
from common_lib import error
+
Testing None
Use "is None" rather than "== None" and "is not None" rather than "!= None".