Update style according to advice from pylint.

Update style according to advice from pylint.

BUG=

Committed: https://crrev.com/0f7acf8eda06bc95341a3869a9e51d48ae2a9a99
Cr-Commit-Position: refs/heads/master@{#302139}

[qyearsley, 2014-10-27 23:40:21]

qyearsley@chromium.org changed reviewers:
+ prasadv@chromium.org, robertocn@chromium.org, sergiyb@chromium.org

[qyearsley, 2014-10-27 23:40:21]

I was just trying to take a look at what tips pylint might give me about long
methods, etc., and I found that the default depot_tools configuration of pylint
isn't giving all the warnings that it could.

This CL fixes some warnings related to:
 * Unnecessary spaces
 * Unnecessary parenthesis
 * Backslashes in strings that don't escape anything, e.g. in regex strings.
Regex strings can be preceded with an "r" to make it clearer that we want
literal backslashes.

[RobertoCN, 2014-10-27 23:47:18]

On 2014/10/27 23:40:21, qyearsley wrote:
> I was just trying to take a look at what tips pylint might give me about long
> methods, etc., and I found that the default depot_tools configuration of
pylint
> isn't giving all the warnings that it could.
> 
> This CL fixes some warnings related to:
>  * Unnecessary spaces
>  * Unnecessary parenthesis
>  * Backslashes in strings that don't escape anything, e.g. in regex strings.
> Regex strings can be preceded with an "r" to make it clearer that we want
> literal backslashes.

LGTM

[qyearsley, 2014-10-28 00:06:22]

On 2014/10/27 23:47:18, robertocn wrote:
> On 2014/10/27 23:40:21, qyearsley wrote:
> > I was just trying to take a look at what tips pylint might give me about
long
> > methods, etc., and I found that the default depot_tools configuration of
> pylint
> > isn't giving all the warnings that it could.
> > 
> > This CL fixes some warnings related to:
> >  * Unnecessary spaces
> >  * Unnecessary parenthesis
> >  * Backslashes in strings that don't escape anything, e.g. in regex strings.
> > Regex strings can be preceded with an "r" to make it clearer that we want
> > literal backslashes.
> 
> LGTM

Hmm, just then I only ran configs/try.py --filter=linux.bisect, there should
only be one try job started.
Something is definitely wrong the configs/try.py script.

[qyearsley, 2014-10-28 00:39:49]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2014-10-28 00:46:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/681103002/1

[commit-bot: I haz the power, 2014-10-28 00:46:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-28 00:46:19]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[qyearsley, 2014-10-29 00:36:35]

On 2014/10/28 00:46:19, I haz the power (commit-bot) wrote:
> No LGTM from a valid reviewer yet. Only full committers are accepted.
> Even if an LGTM may have been provided, it was from a non-committer,
> _not_ a full super star committer.
> See http://www.chromium.org/getting-involved/become-a-committer
> Note that this has nothing to do with OWNERS files.

This needs a review from Prasad or Sergiy before it could be committed.

This isn't an urgent/high-priority CL, review when you have time :-)

[Sergiy Byelozyorov, 2014-10-30 11:42:45]

lgtm with comments

https://codereview.chromium.org/681103002/diff/1/tools/auto_bisect/bisect_pri...
File tools/auto_bisect/bisect_printer.py (right):

https://codereview.chromium.org/681103002/diff/1/tools/auto_bisect/bisect_pri...
tools/auto_bisect/bisect_printer.py:40: | / \\ | questions or suggestions about
bisecting. THANK YOU."""
Another tooth? Please align face boundaries :-).

[qyearsley, 2014-10-30 16:46:05]

https://codereview.chromium.org/681103002/diff/1/tools/auto_bisect/bisect_pri...
File tools/auto_bisect/bisect_printer.py (right):

https://codereview.chromium.org/681103002/diff/1/tools/auto_bisect/bisect_pri...
tools/auto_bisect/bisect_printer.py:40: | / \\ | questions or suggestions about
bisecting. THANK YOU."""
On 2014/10/30 11:42:45, Sergiy Byelozyorov wrote:
> Another tooth? Please align face boundaries :-).

This is actually the same as before -- """\ """ is the same as """\\ """. In
both cases it's a backslash followed by a space. But, if the character following
the backslash was another character, e.g. a "t", then it would be different, so
that's why pylint suggests representing all backslashes as \\.

[qyearsley, 2014-10-30 18:04:59]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2014-10-30 18:06:35]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/681103002/1

[commit-bot: I haz the power, 2014-10-30 19:56:41]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-30 19:58:10]

Patchset 1 (id:??) landed as
https://crrev.com/0f7acf8eda06bc95341a3869a9e51d48ae2a9a99
Cr-Commit-Position: refs/heads/master@{#302139}