[IPython-dev] [patch] IPython.set_trace() implemented

Gökhan SEVER gokhansever@gmail....
Tue Jun 23 00:58:16 CDT 2009


>
> Right, the up/down arrows cycle through the commands that were in
> ipython. It seems that ipython somehow rewrote the python's history.
> But you are *not* running in ipython after exiting it.



Check out this:


[gsever@ccn python-repo]$ python
Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38)
[GCC 4.3.2 20080917 (Red Hat 4.3.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import IPython
>>> IPython.set_trace()
 Logging to /home/gsever/.ipython/2009-06-23.py

Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38)
Type "copyright", "credits" or "license" for more information.

IPython 0.10.bzr.r1174 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object'. ?object also works, ?? prints more.

In [1]: exit()
Do you really want to exit ([y]/n)? y
>>> arr = arange(10)
---------------------------------------------------------------------------
NameError                                     Python 2.5.2: /usr/bin/python
                                                   Tue Jun 23 00:54:55 2009
A problem occured executing Python code.  Here is the sequence of function
calls leading up to the error, with the most recent (innermost) call last.

/home/gsever/Desktop/python-repo/ipython/IPython/FakeModule.pyc in
<module>()
----> 1
      2
      3
      4
      5
      6
      7
      8
      9
     10
     11
     12
     13
     14
     15
     16
     17
     18
     19
     20
     21
     22
     23
     24
     25
     26
     27
     28
     29
     30
     31

NameError: name 'arange' is not defined

**********************************************************************

Oops, IPython crashed. We do our best to make it stable, but...

A crash report was automatically generated with the following information:
  - A verbatim copy of the crash traceback.
  - A copy of your input history during this session.
  - Data on your current IPython configuration.

It was left in the file named:
    '/home/gsever/.ipython/IPython_crash_report.txt'
If you can email this file to the developers, the information in it will
help
them in understanding and correcting the problem.

You can mail it to: Ville Vainio at vivainio@gmail.com
with the subject 'IPython Crash Report'.

If you want to do it now, the following command will work (under Unix):
mail -s 'IPython Crash Report' vivainio@gmail.com <
/home/gsever/.ipython/IPython_crash_report.txt

To ensure accurate tracking of this issue, please file a report about it at:
https://bugs.launchpad.net/ipython/+filebug

Press enter to exit:


This error message tells me that somewhere in the background Ipython is
still active, can't completely kill its instance after exiting the session.


>
> You can use "pdb", or winpdb. There are lots of other options too, see
> this thread on the sage-devel:
>
>
> http://groups.google.com/group/sage-devel/browse_thread/thread/d7fbcf164eaedbc5
>
> Ondrej


Thanks for the exact link ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/ipython-dev/attachments/20090623/078f1c62/attachment.html 


More information about the IPython-dev mailing list