-
Notifications
You must be signed in to change notification settings - Fork 767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IntelliSence issues #105
Comments
Addressing each of these:
|
Thank you for your answer.
In Python 3.8.0 with NumPy 1.18.0: In Python 3.7.2 with NumPy 1.16.2: NumPy was installed with pip in both cases.
|
Can you try again with numpy 1.19? I'm thinking that their stubs are now included, so I'm curious if this improves things.
We don't want to do this without some careful planning, at least not at the moment. This means calling out to python and executing the code to gain its info; it's not static and is pretty imperfect. |
With NumPy 1.19.1, the result is the same as with 1.18.0, which was already good enough for me. |
It was an issue already in the previous Python extension: in quick info, line breaks are poorly handled. For example, now I use Google-style docstrings in a project, and the whole text appears without any line breaks in quick info. At NumPy, titles (Parameters, Returns, See Also, etc.) rendered adequately; however, the list of parameters follow each other without any breaks.
Quick info hides the function annotation and provides type information instead. That's a problem because the docstrings usually refer to parameter names which are lost. (E.g. first line in quick info of
np.mean
is this:(function) mean: Any | _AnyCallable
, while first line produced byhelp(np.mean)
ismean(a, axis=None, dtype=None, out=None, keepdims=<no value>)
.) Parameter info also suffer from this and cannot help the calling.There is no information about functions of OpenCV, despite
help
works properly (and so the old Python extension could fetch quick info and parameter info as well). What is worst, that some built-in functions (for exampleopen
,len
, etc.) and some standard library functions (os.remove
,os.path.join
,random.seed
,random.randint
) lack of proper quick info, meanwhile others work well (glob.glob
,re.sub
,subprocess.Popen
).I'm using v2020.7.1 of Pylance, 3.8.0 of Python, 1.47.0 of VSCode on Win10.
By the way, I like your new extension and hope it'll be successful.
The text was updated successfully, but these errors were encountered: