formatOnType will change two spaces before comment to one

[MisLink]

Environment data

• VS Code version: 1.23.1
• Extension version (available under the Extensions sidebar): 2018.5.0-rc
• OS and version: MacOS 10.13.4
• Python version (& distribution if applicable, e.g. Anaconda): CPython 3.6.5
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
• Relevant/affected Python packages and their versions: XXX

Actual behavior

a = 1  # two spaces before hash sign
<enter>
a = 1 # one left

Expected behavior

keep two spaces.

BTW, I notice this feature is being considered for deletion (#1586), is this kind of issues welcome?

Steps to reproduce:

1. XXX

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

XXX

[brettcannon]

Yep, this info is still welcome as we're re-evaluating whether to keep or remove the feature so bug reports like this are still useful.

[brettcannon]

PEP 8 says to use two spaces from the statement.

[MikhailArkhipov]

@MisLink - yes please. This one is trivial to adjust. Do you have the feature on a regular basis?

[MisLink]

well, use frequency of inline comments is very low for me.

[MikhailArkhipov]

I meant the feature itself (i.e. format on type) :-)

[MisLink]

oh sorry, I misunderstand your meaning...
I take this feature as my default global setting.