Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Display of "Canopy" on command line

I have a basic terminal question. I just installed enthought's Canopy for Python on Snow Leopard, and (Canopy 64bit) continually shows up when I'm working on the command line.

EX: (Canopy 64bit) Macbook~[username]$

I've tried editing my bashrc file, to no avail.

bashrc currently has this:

# System-wide .bashrc file for interactive bash(1) shells.
if [ -z "$PS1" ]; then
   return
fi

PS1="Macbook~\u\$"
# Make bash check its window size after a process completes
shopt -s checkwinsize

--

Is there any way to stop "(Canopy 64bit)" from displaying?

like image 381
user2269080 Avatar asked Apr 11 '13 06:04

user2269080


1 Answers

To elaborate on previous answers: Canopy is based on a 3-layers system, layer 0 contains the bare minimum for the Canopy GUI to work; layer 1 contains all of the "System" packages, which are distributed with Canopy and may be updated when new versions come out; finally, layer 2 is the "User" environment where users can install any package they like. In this way, if the user installs a package that breaks Canopy, one may always fall back to layer 1, or even layer 0 to do a system reset.

The three layers are managed using a popular library, virtualenv. In virtualenv, you can create isolated Python environments with their own set of libraries. For example, if you are developing several application, each requiring conflicting packages, you can develop them in separate "virtual environments". Using virtualenv, Canopy is able to do the same: you may have multiple "User" environment (although that feature is not exposed through the GUI yet).

One activates a virtual environment using its "activate" script, which Canopy does in the .bash_profile line

~/Library/Enthought/Canopy_64bit/User/bin/activate

as pointed out by DJon .

By default, virtualenv modifies your bash prompt so that you can remember which virtual environment you are in, that's why you see the "(Canopy 64bit)" prompt. To get rid of it, you can remove the line from .bash_profile, but this means that you will have to manually point your system to the right python executable and the right libraries.

punchagan solution simply deactivates the default virtualenvprompt, leaving the Canopy virtual environment itself intact:

VIRTUAL_ENV_DISABLE_PROMPT=true

like image 176
pberkes Avatar answered Sep 18 '22 13:09

pberkes