PTVS - general IntelliSense problems - no error highlighting, no recognition of modules from other projects

829 views Asked by At

I have used PTVS for two years now, and I remember (am I going crazy?) that PTVS always highlighted errors when working on a .py file in Visual Studio.

As of ~ Oct 10th (possible connected with v15.4 of VS2017), there have been issues with PTVS. In my frustration, I have completely reinstalled windows and wiped the entire computer clean. After installing drivers, I installed VS using the Visual Studio 2017 Community installer with the following options:

enter image description here

I then open Visual Studio, create a new empty python project, and type some garbage. No. Error. Correcting.

enter image description here

Am I going mad?

My python environment autocompletion / intellisense database is refreshed, by the way.

enter image description here

Meanwhile, the "View->Error List" window shows errors, even though they aren't highlighted. enter image description here

Uninstalled the "Python native development tools" extension, still does not work. Installed with bare minimum python options (python language support, python 3.6, templates). Doesn't work.

Not sure if this is related (it probably is), Intellisense fails to recognize modules from other projects using any method. This was fine a week ago: (note green squiggles are Intellisense "Cannot resolve" errors) enter image description here

3

There are 3 answers

2
Jack Zhai On BEST ANSWER

I got the same issue as yours, but it could show the Red color in VS2015.

enter image description here

For this issue, I help you report this issue to the developer community site:

https://developercommunity.visualstudio.com/content/problem/132688/ptvs-general-intellisense-problems-no-error-highli.html

You could add your comment there.

For the second issue, about the module reference. Not the real Python team members, but maybe you could find a way here:

How to import functions from other projects in Python?

One thread for one issue, maybe you could start a new python issue for it.

1
JoseOrtiz3 On

There was a bug in VS 2017 15.4, and apparently it will be fixed upon next release. For anyone experiencing these issues, VS 2015's Python Tools work if you need any of these functionalities.

0
dev-masih On

This is a bug that fixed on 31 October 2017 with Update 15.4.2

Source