Skip to content
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

Auto-detect crashes with Python 3.6 64-bit #1994

Closed
r0f1 opened this issue Dec 27, 2016 · 7 comments
Closed

Auto-detect crashes with Python 3.6 64-bit #1994

r0f1 opened this issue Dec 27, 2016 · 7 comments
Assignees
Labels
Milestone

Comments

@r0f1
Copy link

r0f1 commented Dec 27, 2016

Hi,
I downloaded and installed 'Python 3.6.0 - 2016-12-23', 64-bit version from the python website. After opening VS, I saw, that the new environment was not recognized, in the Python Environment tab, so I started to add it manually. However, when I wanted to select the version, there was no option for 3.6 (only 3.5), so I clicked on "Auto-detect". Then VS crashed.
After a restart, all of my exsisting Python Environments were gone and the "+ Custom" button was greyed out. Also, navigating to the "Python Tools" section of the "Options", I saw that I have "no environments installed" and everything was greyed out over there as well.

I am now uninstalling Python 3.6 and reinstalling VS+PTVS. Just thought you should know.
Best, r0f1

UPDATE: The new installation did not help. But I got my python environments back by editing the registry: I navigated to

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\PythonTools\Interpreters

There was one folder in this directory (and some of the keys told me that the version was indeed the one that I added with version 3.6). After deleting the folder, everything was back to normal.

@zooba zooba changed the title VS Crashes with Python 3.6 64-bit Auto-detect crashes with Python 3.6 64-bit Dec 27, 2016
@zooba
Copy link
Member

zooba commented Dec 27, 2016

I believe this is just the auto-detection crashing. You should be able to select "3.5" from the drop-down and fill in the other information by hand (nothing apart from the directory has changed from 3.5).

You won't get any support for the new syntax in 3.6, but that's the nature of software updates. We don't have any updates planned for VS 2015 any more, but VS 2017 has proper support for 3.6, as well as a fix for this particular crash.

@r0f1
Copy link
Author

r0f1 commented Dec 27, 2016

Thanks!

@r0f1 r0f1 closed this as completed Dec 27, 2016
@zooba zooba added this to the 2.2.6 milestone Jan 2, 2017
@zooba zooba reopened this Jan 2, 2017
@zooba zooba self-assigned this Jan 3, 2017
@zooba zooba added Build bug and removed Build labels Jan 3, 2017
zooba added a commit to zooba/PTVS that referenced this issue Jan 3, 2017
…hes with Python 3.6 64-bit

Improves handling when loading invalid version numbers from the registry
Prevents unsupported version numbers being auto-detected when configuring an environment.
zooba added a commit that referenced this issue Jan 3, 2017
Fixes #1565, #1994, #2005 Auto-detect crashes with Python 3.6 64-bit
@zooba zooba closed this as completed Jan 3, 2017
@zooba
Copy link
Member

zooba commented Jan 4, 2017

There is a 2.2.6 RC release at https://github.com/Microsoft/PTVS/releases/tag/v2.2.6-rc with the fix for this issue. Please try it out and let us know if anything goes horribly wrong - we want to push the fix to all users within the next month.

@hickford
Copy link

hickford commented Jan 21, 2017

Hi @zooba. I installed that RC. PVTS still doesn't discover Python 3.6 by itself, but the 'auto detect' button worked after I completed 'prefix path'.

Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 08:06:12) [MSC v.1900 64 bit (AMD64)] on win32

@zooba
Copy link
Member

zooba commented Jan 23, 2017

@hickford The auto-detect we are referring to is when you are adding it as a custom Python environment. PTVS in VS 2015 does not support Python 3.6, and so it will never automatically detect it completely, but you can pretend that it is Python 3.5 and it will work well enough.

VS 2017 properly supports Python 3.6, and automatically detects it as soon as you install it.

@hickford
Copy link

Thanks @zooba . Installed Visual Studio 2017 RC and now using it with Python 3.6. Really impressed by PTVS, I love the profiler and the debugger.

@csiege
Copy link

csiege commented May 23, 2017

@zooba, hit this problem on VS2015. Thanks for your post, installing latest PVTS and was able to get custom option working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants