Conflicting commands in vscode-python & vscodeJupyter

[osya]

Environment data

VS Code version: 1.20.1
Python Extension version: 2018.1.0
Python Version: 3.6.4
OS and version: Windows 10 x64 Pro

Actual behavior

Conflicting commands which exists in both vscode-python & vscodeJupyter extensions: runSelectionLine, execCurrentCell, execCurrentCellAndAdvance, gotToPreviousCell, gotToNextCell

Expected behavior

Expected nothing conflicted commands in these two extensions

Steps to reproduce:

Install extensions vscode-python & vscodeJupyter, open Developer Tools Console and see messages there

Logs

Output from Console window (Help->Developer Tools menu)

extensionService.ts:791 [C:\Users\info_000\.vscode\extensions\ms-python.python-2018.1.0]: Command `jupyter.runSelectionLine` appears multiple times in the `commands` section.
extensionService.ts:791 [C:\Users\info_000\.vscode\extensions\ms-python.python-2018.1.0]: Command `jupyter.execCurrentCell` appears multiple times in the `commands` section.
extensionService.ts:791 [C:\Users\info_000\.vscode\extensions\ms-python.python-2018.1.0]: Command `jupyter.execCurrentCellAndAdvance` appears multiple times in the `commands` section.
extensionService.ts:791 [C:\Users\info_000\.vscode\extensions\ms-python.python-2018.1.0]: Command `jupyter.gotToPreviousCell` appears multiple times in the `commands` section.
extensionService.ts:791 [C:\Users\info_000\.vscode\extensions\ms-python.python-2018.1.0]: Command `jupyter.gotToNextCell` appears multiple times in the `commands` section.

I also tried to register issue there Conflicting commands in vscode-python & vscodeJupyter

[osya]

what?

…

On Sun, Feb 25, 2018 at 11:16 PM, Don Jayamanne ***@***.***> wrote: Please could you create an issue for this PR. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#897 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA89Aa-wpzLQGTuqvqa-WN8cBrhB0JwFks5tYb-CgaJpZM4SSbfn> .

-- BR, Valeriy Osipov

[DonJayamanne]

Lol, deleted that comment as soon I realized this wasn't a PR, for some reason I assumed this was a PR.