ActivateState, EPD, Canopy, PythonXY, ...: better discovery


let's get all their reg keys & find them for a better installation experience.


RickWinter wrote Aug 28, 2013 at 6:46 PM

Default installations are detected as CPython's. Canopy 1.1 works nicely. To improve this scenario we'll be adding a custom interpreter example.

RickWinter wrote Sep 25, 2013 at 3:57 PM

New sample code added for extending interpreter registration

nicktp wrote Dec 17, 2013 at 2:43 PM

I have encountered an interesting 'bug' as a result of the auto-detection. I'm running VS Professional 2012 version 11.0.61030.00 Update 4 and PTVS 2.0.11016.00 with 64 bit Enthought Canopy

When I installed Canopy, I did it 'for all users' rather than for a single user. This put my 'core' install in
C:\Program Files\Enthought with two virtual environments in C:\Users[USERNAME]\AppData\Local\Enthought\Canopy.

PTVS auto-detected my installation and created an environment. This gave me a largely working environment with completion for site-packages that I installed but I didn't get completion for standard library packages (eg os, sys, and unittest) and the Test Explorer wouldn't locate any unit tests.

I noticed that when I deleted my completion db and restarted VS, the Test Explorer did find my unit tests but as soon as the completion db had been refreshed, they disappeared again. I believe this is because the completion db did not find unittest package as the Library Path was set incorrectly.

The solution was to manually specify an environment as per http://stackoverflow.com/questions/19572971/canopy-with-visual-studio but using my c:\program files location for the Library Path. Once I had refreshed my completion db the test explorer could find my unit tests again and I also had completion for standard library packages.

Is it possible to auto-detect the two standard installation setups for Canopy?