Unfortunately, the places in code where we default to 2.7 are not suitable for deeper inspection (we can't run python.exe and ask it, for example), so when we encounter an invalid version number choosing the default is the only realistic option. That shouldn't affect anything except syntax errors in the editor, but possibly some saved selections are now confused about which environment to use (for example, something is looking for "2.7" and having to choose between two different 2.7's, whereas before there was only one).Įditing the custom environment and selecting "3.5" as the version should get you as close as is possible. If you previously had a custom environment set up for 3.6 that was breaking VS, we probably automatically changed the version to 2.7 (which is the default version everywhere throughout that version of PTVS). Visual Studio 2015 > Microsoft Visual Studio 2015 Visual Studio ' ' > Visual Studio Python ' ' Visual Studio Python Visual Studio 2015 Python 3. The component model cache problem is a VS bug that won't be fixed, but restarting VS should resolve it (as the message suggests).
0 Comments
Leave a Reply. |