##// END OF EJS Templates
Handle OSError cases where traceback frames occur from built files (#13964)...
Handle OSError cases where traceback frames occur from built files (#13964) I've been using the `_render_traceback_` method of the traceback object, provided by the `IPython.core.interactiveshell.InteractiveShell` object that you created, in the `showtraceback` method. Thanks to this, I was able to create better error messages. I appreciate it. The following issue is related to the use of this method. ```python try: # Exception classes can customise their traceback - we # use this in IPython.parallel for exceptions occurring # in the engines. This should return a list of strings. if hasattr(value, "_render_traceback_"): stb = value._render_traceback_() else: stb = self.InteractiveTB.structured_traceback( etype, value, tb, tb_offset=tb_offset ) ``` I noticed that in the recent `8.11` version, code was added to generate a traceback when the source code is too long. In this case, if the `etb.tb_frame` object is a built file or something similar, the `inspect.getsourcelines(etb.tb_frame)` method may raise an error. So I implemented a change to set the `max_len` to the minimum value and avoid the following condition when an `OSError` occurs. I think this approach can handle cases where errors occur while using the `inspect.getsourcelines()` method. If there is anything I have done wrong or any procedures I should follow, please let me know. I would greatly appreciate it if you could leave a comment and I will make the necessary changes immediately. Thank you.

File last commit:

r27637:9f3065cb
r28196:92027083 merge
Show More
index.rst
116 lines | 3.1 KiB | text/x-rst | RstLexer

IPython Documentation

Welcome to the official IPython documentation.

IPython provides a rich toolkit to help you make the most of using Python interactively. Its main components are:

  • A powerful interactive Python shell.

    Screenshot of IPython 6.0
  • A Jupyter kernel to work with Python code in Jupyter notebooks and other interactive frontends.

The enhanced interactive Python shells and kernel have the following main features:

  • Comprehensive object introspection.
  • Input history, persistent across sessions.
  • Caching of output results during a session with automatically generated references.
  • Extensible tab completion, with support by default for completion of python variables and keywords, filenames and function keywords.
  • Extensible system of 'magic' commands for controlling the environment and performing many tasks related to IPython or the operating system.
  • A rich configuration system with easy switching between different setups (simpler than changing $PYTHONSTARTUP environment variables every time).
  • Session logging and reloading.
  • Extensible syntax processing for special purpose situations.
  • Access to the system shell with user-extensible alias system.
  • Easily embeddable in other Python programs and GUIs.
  • Integrated access to the pdb debugger and the Python profiler.

The Command line interface inherits the above functionality and adds

  • real multi-line editing thanks to prompt_toolkit.
  • syntax highlighting as you type.
  • integration with command line editor for a better workflow.

The kernel also has its share of features. When used with a compatible frontend, it allows:

  • the object to create a rich display of Html, Images, Latex, Sound and Video.
  • interactive widgets with the use of the ipywidgets package.

This documentation will walk you through most of the features of the IPython command line and kernel, as well as describe the internal mechanisms in order to improve your Python workflow.

You can find the table of content for this documentation in the left sidebar, allowing you to come back to previous sections or skip ahead, if needed.

The latest development version is always available from IPython's GitHub repository.