Allow doule indentation for function definitions

[LefterisJP]

Many projects use double indentation for function definition arguments. That is in order to allow the arguments to be clearly separated and visible.

I have not found a configuraion/knob to allow this with yapf. No matter my config it always try to go only for single indentation. How could I make the following not be changed?

     def create_oracle_cache(
-            self,
-            oracle: HistoricalPriceOracle,
-            from_asset: AssetWithOracles,
-            to_asset: AssetWithOracles,
-            purge_old: bool,
+        self,
+        oracle: HistoricalPriceOracle,
+        from_asset: AssetWithOracles,
+        to_asset: AssetWithOracles,
+        purge_old: bool,
     ) -> None:

Keep in mind the double indentation is only for function definitions. Everywhere else it should be single.

Related issue but still no solution: #843

[LefterisJP]

A way around this is to use a different tool to perform this change, after yapf runs. A fork of double-indent I made seems to work fine: https://github.com/LefterisJP/double-indent

The problem is that:

1. You need a different tool, running after yapf at --in-place mode.
2. You can no longer use yapf to do anything but reformat (with --in-place) since it will always find the double indentation problem

[CSatSVFX]

Not quite everywhere else as if statements have the same issue. It seems to be anywhere that a new code block/indentation happens, though as mentioned in that other ticket, bad continuation was removed from the more recent versions of pylint as can be seen here: pylint-dev/pylint#3571

I do understand and commiserate if you aren't able to simply update your pylint version however and still would like the flexibility.

[LefterisJP]

I do understand and commiserate if you aren't able to simply update your pylint version however and still would like the flexibility.

What does that have to do with anything? Pylint can't auto-format your code. The issue is about yapf allowing this option as a customization.

Unless you are trying to say this kind of styling is outdated and should not be followed?