Have hover popups for class instantiation also show constructor docstring

[mawright]

Environment data

• VS Code version: 1.25.1
• Extension version (available under the Extensions sidebar): 2018.6.0
• OS and version: Ubuntu 16.04
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda, 3.6.6
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• Relevant/affected Python packages and their versions: N/A

Actual behavior

Here's some screenshots:

Note that in both screenshots, the hover popup only shows the Class docstring.

Note: If there is no class docstring, the hover popup has no docstring info.

Expected (requested?) behavior

Hover popup would include constructor docstring. This is how e.g., IPython behaves.

Python 3.6.6 |Anaconda, Inc.| (default, Jun 28 2018, 17:14:51) 
Type 'copyright', 'credits' or 'license' for more information
IPython 6.4.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import test

In [2]: test.TestClass?
Init signature: test.TestClass(my_param)
Docstring:      Class docstring
Init docstring: Constructor docstring
File:           ~/Code/test/test.py
Type:           type

Steps to reproduce:

N/A

Thanks for the work on the great extension.

[mawright]

Hi @brettcannon, sorry if my original title wasn't clear.

Your title change describes the current behavior. That is that only the class dosctring is shown on the hover popups when you are instantiating a class.

The constructor dosctring is not shown. This means one needs to use something other than the hover popups to find the constructor documentation if init is not documented in the class docstring.

[dukduque]

It would be nice if the constructor docstring just follow right after the class docstring.

[jakebailey]

This looks like an old issue, and has been fixed for a while now:

Closing.

[celynw]

Is there some kind of setting which could be overriding this?
It's always been like this for me and I was surprised to find it fixed.

• VS Code version: 1.40.1
• Extension version (available under the Extensions sidebar): 2019.11.50794
• OS and version: Ubuntu 16.04
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda, 3.7.3
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• Relevant/affected Python packages and their versions: N/A

EDIT: Ah! Yes. The setting python.jediEnabled is set by default, which overrides the Microsoft Python Analysis Engine. I wasn't even using this, it seems!
Tried it again and works as expected

[jakebailey]

Yes, if jedi's enabled, we're not, so it'd be a bug on jedi itself. Thanks for checking.