Make CONTINUATION_INDENT_WIDTH configurable.

[zhou13]

Current vim will indent as

tf.app.flags.DEFINE_string(
  'log', 'INFO',
  'The threshold for what messages will be logged DEBUG, INFO, WARN, ERROR, '
  'or FATAL.')

with sw=2. However, I want to have the following indent (google style):

tf.app.flags.DEFINE_string(
    'log', 'INFO',
    'The threshold for what messages will be logged DEBUG, INFO, WARN, ERROR, '
    'or FATAL.')

In yapf, this is configurable by option CONTINUATION_INDENT_WIDTH.

[blueyed]

What is yapf?
And why would you use sw=2 with Python files?

[zhou13]

What is yapf?

https://github.com/google/yapf

And why would you use sw=2 with Python files?

That is in google's internal Google Python Style guide. Many open source libraries from google such as tensorflow follow this convention, e.g., https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/bayesflow/python/kernel_tests/monte_carlo_test.py

Also see,
https://www.chromium.org/chromium-os/python-style-guidelines

[blueyed]

So they use 2 spaces instead of 4 for indentation, but then 4 for something else?! / hanging indents?!

[blueyed]

(havent't checked the specific links (the last 2 ones))

[zhou13]

Yes, as shown in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/bayesflow/python/kernel_tests/monte_carlo_test.py

[blueyed]

Ok, feel free to get this integrated somehow here - I am not much interested myself.

Maybe it could be defined as something like 2 * &sw in special cases?!

[zhou13]

I prefer hard code it to 4, as both pep8 and google prefer this value.

[blueyed]

Then do it.. :)

(but be warned that the current test suite is rather ugly)

[zhou13]

Please review #79