ipython command does not work in terminal

[mcooganj]

I tried easy_install, pip install and git cloning ipython down. All worked, but none enabled the command $ ipython at the terminal.

after cloning ipython built just fine, and$ python ipython.py works to start python inside the directory. i can also import IPython inside a python session -- however ipython does not work at the terminal (which is annoying, as i am used to it working now).

I am pretty sure this is just a alias gone awry, but i don't know how to fix it -- could someone please help?

[takluyver]

If you type alias in a terminal, it should show you any shell aliases you have defined. Other than that, make sure it's installing scripts to somewhere on your $PATH.

[mcooganj]

How can i check where it installs scripts?

On 22/02/2013, at 11:17 PM, Thomas Kluyver notifications@github.com wrote:

If you type alias in a terminal, it should show you any shell aliases you
have defined. Other than that, make sure it's installing scripts to
somewhere on your $PATH.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/2969#issuecomment-13940629.

[mcooganj]

I am working with a clean mountain lion install, so alias does not return
anything.

On 22/02/2013, at 11:17 PM, Thomas Kluyver notifications@github.com wrote:

If you type alias in a terminal, it should show you any shell aliases you
have defined. Other than that, make sure it's installing scripts to
somewhere on your $PATH.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/2969#issuecomment-13940629.

[mcooganj]

sorry to bother -- i simply hadn't yet added /usr/local/share/python: to my
paths.

On 23 February 2013 08:12, Matthew Johnson mcooganj@gmail.com wrote:

I am working with a clean mountain lion install, so alias does not return
anything.

On 22/02/2013, at 11:17 PM, Thomas Kluyver notifications@github.com
wrote:

If you type alias in a terminal, it should show you any shell aliases you
have defined. Other than that, make sure it's installing scripts to
somewhere on your $PATH.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2969#issuecomment-13940629.

[takluyver]

No worries. For future reference, this kind of question is better dealt with on the mailing list, or on our new chat room. The issue tracker is for things that need to be fixed in IPython.

[mcooganj]

Understood. Thanks

On 23/02/2013, at 10:24 AM, Thomas Kluyver notifications@github.com wrote:

No worries. For future reference, this kind of question is better dealt
with on the mailing list, or on our new chat
roomhttp://www.hipchat.com/ghSp7E1uY.
The issue tracker is for things that need to be fixed in IPython.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/2969#issuecomment-13979256.