PTVS 2.1 Refreshing DB Hangs with Python 3.4

Nov 6, 2014 at 1:00 AM
I'm with VS 2010 with PTVS 2.1 and Python 3.4 (with no additional packages) and the completion DB seems to be in an infinite loop, taking over an hour before I shutdown VS and kill the Analyzer process.

I have found some other, similar threads but they seem outdated or don't quite apply. Is 'C:\Users\<userid>\AppData\Local\Python Tools\CompletionDB\10.0\2af0f10d-7135-4994-9156-5d01c9c11b7e\3.4\AnalysisLog.txt' the correct log? The last line is "2014-11-05T20:09:04: Starting analysis of 1477 modules" Is that normal?
Coordinator
Nov 6, 2014 at 2:08 AM
An hour is too long, certainly. Do you have the exact version number of the Python you installed? (The filename of the installer would be perfect.)
Nov 6, 2014 at 3:05 AM
Python 3.4.2 (v3.4.2:ab2c023a9432, Oct 6 2014, 22:15:05) [MSC v.1600 32 bit (Intel)] on win32

https://www.python.org/ftp/python/3.4.2/python-3.4.2.msi
Coordinator
Nov 6, 2014 at 4:11 AM
That's very strange, I've been using that version since it was released. I'll try some things tomorrow and see if I can figure out what may be going on.
Nov 6, 2014 at 12:16 PM
Edited Nov 6, 2014 at 12:17 PM
Is there any other diagnostic tool that I can enable?

Is the LogPath Registry Key (from this post) still valid?
Coordinator
Nov 6, 2014 at 12:55 PM
Yep, if you want to produce that log and email it to ptvshelp@microsoft.com, that'd be helpful.
Nov 6, 2014 at 4:43 PM
I created the key Analysis\StandardLibrary with the string value LogPath set to D:\log.csv in the my registry so that I have
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\PythonTools\Analysis\StandardLibrary\LogPath
After killing the process and re-launching VS and manually clicking the refresh db button, no log appeared. And I still get stuck.

I expected to see a /diag command switch in the command line but I don't see it:

"C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft\Python Tools for Visual Studio\2.1\Microsoft.PythonTools.Analyzer.exe" /id {2af0f10d-7135-4994-9156-5d01c9c11b7e} /version 3.4 /python C:\Progra~1\Python34\python.exe /library C:\Progra~1\Python34\lib /outdir "C:\Users\sakahira\AppData\Local\Python Tools\CompletionDB\10.0\2af0f10d-7135-4994-9156-5d01c9c11b7e\3.4" /basedb "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft\Python Tools for Visual Studio\2.1\CompletionDB" /log "C:\Users\sakahira\AppData\Local\Python Tools\CompletionDB\10.0\2af0f10d-7135-4994-9156-5d01c9c11b7e\3.4\AnalysisLog.txt" /glog "C:\Users\sakahira\AppData\Local\Python Tools\CompletionDB\10.0\AnalysisLog.txt" /wait ""
Coordinator
Nov 6, 2014 at 6:17 PM
Does your user have permission to write to D:\?

You won't see the extra option added to the command line as we pick up the registry key inside the analyzer. However, if you want to add /diag D:\log.csv to that command line and execute it yourself, that will work too.
Nov 6, 2014 at 6:32 PM
In the end I had to manually execute the command line with the /diag option. The registry key does not work for me.
Dec 22, 2014 at 10:24 AM
replace python msi from x86 to x86-64

good luck
Jan 7, 2015 at 4:25 AM
Zooba wrote:
Yep, if you want to produce that log and email it to ptvshelp@microsoft.com, that'd be helpful.
After re-installing PTVS and Python 3.4.2 I am still hanging. I've e-mailed ptvshelp@microsoft.com the log.csv file.
Jan 13, 2015 at 12:17 AM
I figured it out with Zooba's help. Here's the related work item: https://pytools.codeplex.com/workitem/2838.