function parameter hover card does not close when using IntelliSense within it

[ghost]

Environment data

VS Code version: 1.19.1(1.19.1)
Python Extension version: 0.9.1
Python Version: 3.6.3
OS and version: macOS High Sierra 10.13.2(17C88)

Actual behavior

1. key stroke "print(" -> function popup start
2. key stroke ")" -> function popup close, but...
3. key stoke "alt+enter" -> function popup not close

Expected behavior

3. key stoke "alt+enter" -> function popup close

Steps to reproduce:

1. key stroke "print(" -> function popup start
2. key stroke ")" -> function popup close
3. key stoke "alt+enter" -> function popup close

Logs

Output from Python output panel

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

[brettcannon]

I think this is a VS Code issue and not us since we don't forcibly create the pop-up, just populate it when VS Code requests that we do.

[ghost]

Hi brettcannon.
Today I got vscode's comment. here
microsoft/vscode#41591

sorry my english. i'm korean. i use Python with Python Extension and Sublime keybinding.
If i press ( vscode automatically make ) too.
So when I input arguments and want move next line, without pressing ) + Enter, I just press Command+Enter
I aleady work next line, but function popup keep going.
reference screenshot image
https://imgur.com/a5ffQcV

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. Happy Coding!

Ok, please file this issue then against the Phyton Extension because that determines when to close the pop up.

[brettcannon]

I've re-opened this.

[ericsnowcurrently]

I've been able to reproduce similar broken behavior (on linux) with the following:

print(f'')
range()

(The popup switches back to "function print ...".)

Whereas the following does not have the problem:

print('')
range()

So I expect that the problem is with some contextual information that the python extension is sending to VSC.

Also, I have the problem the same with and without alt+enter.

[MikhailArkhipov]

#187 - Jedi does not understand f-strings

[ericsnowcurrently]

Right. It was just a simple alternative repro of the problem, in hopes that it points to the problem. :)

[brettcannon]

This seems to have been fixed. If we are wrong then please let us know.