I can blow up any Python Tools installation in VS 2010 Win7 64bit by using isinstance() with a variable, such as:
If I type this in the source code editor or the interpreter, within 1-2 seconds I am guaranteed a blowup.
Any variable name and any type.
Now, I have used isinstance before in my code and have not seen this before, but I some changes per Dinov's suggestions to some debug py files to allow multithreading in the PTVS. And now I see this behavior. So I don't know if this is related
Have tried this on two Win7 machines...one was a VM and the other a regular install on hardware. Both cases win7 64bit. So I know this is unlikely to be a machine or install-specific problem.
Net net, I can't use the isinstance function...something in intellisense really doesn't like it and blows up visual studio predictably and every time.
Any ideas? I kind of need isinstance to work.