<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Right, the up/down arrows cycle through the commands that were in<br>
ipython. It seems that ipython somehow rewrote the python's history.<br>
But you are *not* running in ipython after exiting it.</blockquote><div><br><br>Check out this:<br><br><br>[gsever@ccn python-repo]$ python<br>Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38) <br>[GCC 4.3.2 20080917 (Red Hat 4.3.2-4)] on linux2<br>
Type "help", "copyright", "credits" or "license" for more information.<br>>>> import IPython<br>>>> IPython.set_trace()<br> Logging to /home/gsever/.ipython/2009-06-23.py<br>
<br>Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38) <br>Type "copyright", "credits" or "license" for more information.<br><br>IPython 0.10.bzr.r1174 -- An enhanced Interactive Python.<br>? -> Introduction and overview of IPython's features.<br>
%quickref -> Quick reference.<br>help -> Python's own help system.<br>object? -> Details about 'object'. ?object also works, ?? prints more.<br><br>In [1]: exit()<br>Do you really want to exit ([y]/n)? y<br>
>>> arr = arange(10)<br>---------------------------------------------------------------------------<br>NameError Python 2.5.2: /usr/bin/python<br> Tue Jun 23 00:54:55 2009<br>
A problem occured executing Python code. Here is the sequence of function<br>calls leading up to the error, with the most recent (innermost) call last.<br><br>/home/gsever/Desktop/python-repo/ipython/IPython/FakeModule.pyc in <module>()<br>
----> 1 <br> 2 <br> 3 <br> 4 <br> 5 <br> 6 <br> 7 <br> 8 <br> 9 <br> 10 <br> 11 <br> 12 <br> 13 <br> 14 <br> 15 <br> 16 <br> 17 <br> 18 <br> 19 <br>
20 <br> 21 <br> 22 <br> 23 <br> 24 <br> 25 <br> 26 <br> 27 <br> 28 <br> 29 <br> 30 <br> 31 <br><br>NameError: name 'arange' is not defined<br><br>**********************************************************************<br>
<br>Oops, IPython crashed. We do our best to make it stable, but...<br><br>A crash report was automatically generated with the following information:<br> - A verbatim copy of the crash traceback.<br> - A copy of your input history during this session.<br>
- Data on your current IPython configuration.<br><br>It was left in the file named:<br> '/home/gsever/.ipython/IPython_crash_report.txt'<br>If you can email this file to the developers, the information in it will help<br>
them in understanding and correcting the problem.<br><br>You can mail it to: Ville Vainio at <a href="mailto:vivainio@gmail.com">vivainio@gmail.com</a><br>with the subject 'IPython Crash Report'.<br><br>If you want to do it now, the following command will work (under Unix):<br>
mail -s 'IPython Crash Report' <a href="mailto:vivainio@gmail.com">vivainio@gmail.com</a> < /home/gsever/.ipython/IPython_crash_report.txt<br><br>To ensure accurate tracking of this issue, please file a report about it at:<br>
<a href="https://bugs.launchpad.net/ipython/+filebug">https://bugs.launchpad.net/ipython/+filebug</a><br><br>Press enter to exit:<br><br><br>This error message tells me that somewhere in the background Ipython is still active, can't completely kill its instance after exiting the session.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>You can use "pdb", or winpdb. There are lots of other options too, see<br>
this thread on the sage-devel:<br>
<br>
<a href="http://groups.google.com/group/sage-devel/browse_thread/thread/d7fbcf164eaedbc5" target="_blank">http://groups.google.com/group/sage-devel/browse_thread/thread/d7fbcf164eaedbc5</a><br>
<font color="#888888"><br>
Ondrej</font></blockquote><div><br>Thanks for the exact link ;) <br></div></div><br>