On type formatting errors for args and kwargs

[DonJayamanne]

    def notify(self, *args, **kwargs):

• Use the above code
• Place cursor after the :
• Hit enter

    def notify(self, * args, ** kwargs):

@brettcannon Personally I don't think we should be doing this. What do you think?

[MikhailArkhipov]

Probably should not be doing this.

[MisLink]

f-string has same issue.

before:
f'hello'

after hit enter:
f 'hello'

[brettcannon]

Is there a way to run the formatter through some well-formatted code to see what changes it would make? Like could we run it against the stdlib and see a diff of what would shift to see if we're making any other errors?

[MikhailArkhipov]

Write TS test and supply file line by line to formatter.formatLine as in suite('Formatting - line formatter'

[MisLink]

I found another problem, it will break relative import:
before:
from . import something
after:
from.import something

I tried development build, but it seems like it remove all formatting config.

[DonJayamanne]

I tried development build, but it seems like it remove all formatting config.

I'm sorry, please could you elaborate on this further.

[MisLink]

oh sorry, I am wrong. I open an old workspace that still contain python.formatting.formatOnSave.

But I cant use dev build normally.

There is no interpreter:

It's my workspace config (It's work in stable version):

Select interpreter command is broken:

So I cant test formatter in dev build.

[DonJayamanne]

Please uninstall the extension and reinstall it.

[MisLink]

Try to uninstall -> del ~/.vscode/extension/ms-python.python-2018.4.0-alpha -> reinstall, still not work.

Here is log:

seems like build-in python basic fail to startup, then extensions relate to python all fail?

[DonJayamanne]

Not really sure what your showing in the screen shot.
Please disable all other extensions, then try loading. If that fails please check stack overflow.

[MisLink]

Thanks for your patience, I'm away from the topic.