Python Forum
MS Visual Studio 2015 and Python 3.7
Thread Rating:
  • 2 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MS Visual Studio 2015 and Python 3.7
#1
I am having difficulty with more recent Python 3.7 interpreters and MS Visual Studio 2015 Pro. When I configure I try and configure the interpreter in the Python Environments window, the IntelliSense configuration 'hangs' and cannot complete. When I use the older Python 2.7, the IntelliSense completes. In fact when I install Python 3.7, Visual Studio does not automatically recognize the interpreter, I have to build a 'Custom' interpreter. Support for Python at MSDN is mediocre, so I posted here. If anyone is familiar with Python and Visual Studio 2015 Pro, any help would be appreciated.

Matt
Reply


Messages In This Thread
MS Visual Studio 2015 and Python 3.7 - by MattSA - Oct-02-2018, 07:11 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Python Coding in Power BI Visual vjrans 0 379 Jan-31-2024, 07:54 AM
Last Post: vjrans
  How to set PYTHONPATH in Visual Studio Code? aupres 5 4,911 Aug-15-2023, 03:51 PM
Last Post: snippsat
  how do I open two instances of visual studio code with the same folder? SuchUmami 3 1,043 Jun-26-2023, 09:40 AM
Last Post: snippsat
  Visual Studio Code NewPi 3 1,170 May-16-2023, 11:13 PM
Last Post: snippsat
  Visual Studio Code venv ibm_db error mesi1000 7 2,997 Nov-13-2022, 12:36 AM
Last Post: snippsat
  debugging help on Visual Studio Code mg24 12 2,198 Oct-02-2022, 12:18 AM
Last Post: mg24
  Problem with importing Python file in Visual Studio Code DXav 7 5,482 Jun-15-2022, 12:54 PM
Last Post: snippsat
  Visual Studio Code Intellisense for Imported Modules Not Working hockinsk 1 2,842 Apr-23-2022, 04:41 PM
Last Post: deanhystad
Photo Visual studio code unable to color syntax on python interpreter tomtom 4 7,226 Mar-02-2022, 01:23 AM
Last Post: tomtom
  compile error Visual Studio Code jamie_01 2 1,766 Jan-25-2022, 09:36 AM
Last Post: Larz60+

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020