1 [[!meta title="How do I make IPython or manage.py shell work on scripts.mit.edu?"]]
2 IPython, a nicer interactive Python shell that is, among other
3 things, used by Django’s “manage.py shell” command, doesn’t work by
4 default on scripts.mit.edu because it isn’t able to write to your
5 \~/.ipython directory. Assuming you don’t already use IPython on
6 Athena, you can create a \~/.ipython directory that will work on
7 scripts as follows, replacing LOCKER with the name of your locker:
9 - Create a temporary \~/.ipython directory and make it accessible
11 **mkdir /mit/**LOCKER**/.ipython**
12 **fs sa /mit/**LOCKER**/.ipython daemon.scripts write**
13 - [Log in to scripts](http://scripts.mit.edu/faq/41/) (ssh
14 LOCKER@scripts) and run **ipython**. Because the .ipython directory
15 exists and is writable, ipython will be able to start, but will not
16 configure itself completely.
18 **\_\_IP.user\_setup(?/mit/LOCKER/web\_scripts/.ipython?,??,?install?)**
19 to create a completely-configured default IPython setup in your
20 web\_scripts directory, which is writable from scripts.mit.edu.
21 - Log out of scripts. Remove the temporary \~/.ipython directory
22 and move the real one in place with
23 **rm -r /mit/**LOCKER**/.ipython**
24 **mv /mit/**LOCKER**/web\_scripts/.ipython /mit/**LOCKER