Uninstalling and resetting Canopy

Puneeth Chaganti

July 13, 2015 17:00

Note: if you are uninstalling because you are having problems and want to do a clean re-install, and you already have the current version of Canopy installed, we suggest just doing steps 4 and 5 from the procedure below. This will be much quicker than a full uninstall & re-install. It only requires deleting some directories, then re-starting Canopy, which will re-create those directories to reset a clean working environment.

Windows

Note: If during install you encountered the error "The specified account already exists", please see this article.

1) From the Canopy preferences menu, Unset Canopy as your default Python (this step is not available on very early versions of Canopy).

2) Restart your computer.

3) Uninstall Enthought Canopy from:

Control Panel > Add/Remove Programs (Windows XP).

Control Panel > Programs and Features (Windows 7, 8, or Vista).

4) For each Canopy user, delete one or more of the directories below, which contain that user's "System" and "User" virtual environments, and any user macros.

Deleting "System" removes the environment where the Canopy GUI application runs; it will be re-created the next time that you start Canopy.

Deleting "User" removes all your installed Python packages; it will be re-created with only the packages bundled into the Canopy installer, the next time that you start Canopy.

Deleting the third directory will remove any Canopy macros which you may have written. It is usually empty.

Note that to see the AppData or Local Settings directories in Windows Explorer, you must set Explorer to show hidden files (Computer / Organize / Folder & Search Options / View / Advanced settings / Show hidden...)

6) (This step is not needed if you plan to re-install Canopy; it is only needed if you are trying to remove Canopy completely): If you did not do step 1 for whatever reason, then manually delete any of the following keys from your Windows registry, if they refer to Canopy:

Note: Sometimes Windows will fail to fully uninstall a program, making it difficult to install a new version or alternative program. To help work around this problem, Microsoft has provided the tiny utility "MsiZap.exe", freely available through the Microsoft platform SDK, and also attached below for convenience (the MD5 hash of this attached file is 8a6469cbed9cde987d12f857dba97640). To forcibly remove all references to your Canopy 64-bit installation, from the Windows registry, type:

msizap T {93D7DF53-FDD4-4270-B83C-1EBC15FA1A87}

For a Canopy 32-bit installation, type:

msizap T {7C13AA42-1B81-4C70-963D-D2772F8D7F33}

In either case, if you still have the Canopy installer file available, you can refer to the installer file instead of specifying the product code; for example:

msizap T canopy-1.5.4-win-64.msi

Mac OSX

1) From the Canopy preferences menu, Unset Canopy as your default Python (this step is not available on very early versions of Canopy).

2) Restart your computer.

3) Remove the following directory:

/Applications/Canopy.app

4) For each Canopy user, delete one or all of the directories below, which contain that user's "System" and "User" virtual environments, and any user macros.

Deleting "System" removes the environment where the Canopy GUI application runs; it will be re-created the next time that you start Canopy.

Deleting "User" removes all your installed Python packages; it will be re-created with only the packages bundled into the Canopy installer, the next time that you start Canopy.

Deleting the third directory will remove any Canopy macros which you may have written. It is usually empty.

6) If you are uninstalling completely, edit the following files to delete any lines which reference Canopy (usually, the Canopy-related lines will have been commented out by step 1 but on some system configurations the lines might remain):

6) If you are uninstalling completely, edit the following files to delete any lines which reference Canopy (usually, the Canopy-related lines will have been commented out by step 1 but on some system configurations the lines might remain):

~/.bashrc~/.bash_profile~/.profile

7) Restart your computer.

Please do not enter support requests in article comments

Please use article comments for suggestions to improve the article. For individual support requests, please follow these guidelines.

Comments

How to re-install completely canopy? Because when I try reinstall does not generate the Enthought directory. Thank you

Puneeth Chaganti
June 19, 2013 18:20

Did you try running Canopy after the install? The ~/Enthought directory is re-created on first run, not on install.

Irais Valencia
June 19, 2013 19:13

Thank you for your kind help. The problem have been solved

Christopher Hagmann
June 24, 2013 20:26

I got rid of all of the files you mentioned (Linux) to prep for a clean re-install. When I re-installed, however, It already had me logged in. How did it know?

Puneeth Chaganti
June 25, 2013 00:37

@Christopher, your username and password are stored in a separate file called ~/.enstaller4rc. This is a file that enpkg uses, as well.

Gab Milch
August 05, 2013 22:50

Hi,

I have removed all directories, subdirectories and lines suggested here for Mac OSX, but it still hasn't removed all canopy files, and it still tries to open python files with canopy (pls see screenshot). What do I do now? (I also had previous version of Enthought, that I delted)

Thanks,

Jonathan March
August 06, 2013 00:46

Also delete the preferences directory ~/.canopy. What other Canopy files are you referring to?

Clearing file associations in OSX is non-trivial, as you will see if you search for "os x clear file association", and we currently do not provide a way to do this, though it clearly would be desireable. You can, however, reset the association of .py files, as described here:

"Please do not enter support requests in article comments"

"Please use article comments for suggestions to improve the article. For individual support requests, please follow these guidelines."

When you go to those guidelines, you will see:

"We encourage edX students to first search for answers and post your questions in the Discussion section at the bottom of your relevant edX Courseware page, so that you and other edX students may learn from each other's experiences. If you cannot find an answer there, you are welcome to post to Stack Overflow as just mentioned. Thank you!"

I am deleting your question here. Please post it to Stack Overflow.

Sebastien CELLES
January 19, 2015 10:40

On Mac OS X I also have a /Library/Frameworks/EPD64.framework/Versions/Current/bin directory which also need to be delete.

because I noticed #PATH="/Library/Frameworks/EPD64.framework/Versions/Current/bin:${PATH}" in .bashrc

Jonathan March
January 19, 2015 13:41

@Sebastien -- To be clear, there was no need to delete the EPD directory; Canopy and EPD and other same-version Pythons can coexist comfortably on Mac OS or Linux (although most Canopy users won't actually need to keep an old EPD directory.) The point, rather, is that you should not have more than one Python distribution on your PATH simultaneously.

Jonathan March
July 15, 2015 22:43

Windows users -- see the new note about Microsoft's useful MsiZap utility: "Note: Sometimes Windows will fail to fully uninstall a program"

Paulo Correia
July 21, 2015 14:53

Hi,
I had version 1.3.0 installed which worked well till some time ago. Today a I always got the very same error I tried to install version 1.5.5. However canopy does not starts giving the following:

canopydataimport package not found
Traceback (most recent call last):
File "build/bdist.macosx-10.6-x8664/egg/canopydataimportaddon/plugin.py", line 120, in verifyuserinstallation
File "/home/paulo/Canopy/appdata/canopy-1.5.5.3123.rh5-x8664/lib/python2.7/site-packages/enstaller/repository.py", line 401, in findlatestpackage
raise NoSuchPackage("No package with name {0!r}".format(name))
NoSuchPackage: No package with name 'canopydataimport'

[1]+ Falha de segmentação (core dumped) ./canopy

I deleted .canopy, Enthought, Canopy and canopy folders, but the problem still remains...
Can you help me??
Thanks