Noisy tracebacks?

There has been a change in how tracebacks are shown when running scripts. Example:

Traceback (most recent call last):
  File "/path/to/my/venv/lib/python3.5/site-packages/IPython/core/interactiveshell.py", line 2881, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-2-fdeb52d5be8d>", line 1, in <module>
    f.something()
  File "/path/to/some/file.py", line 68, in something
    assert 1 is not None
AssertionError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/path/to/my/venv/lib/python3.5/site-packages/IPython/core/interactiveshell.py", line 1821, in showtraceback
    stb = value._render_traceback_()
AttributeError: 'AssertionError' object has no attribute '_render_traceback_'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/path/to/my/venv/lib/python3.5/site-packages/IPython/core/ultratb.py", line 1132, in get_records
    return _fixed_getinnerframes(etb, number_of_lines_of_context, tb_offset)
  File "/path/to/my/venv/lib/python3.5/site-packages/IPython/core/ultratb.py", line 313, in wrapped
    return f(*args, **kwargs)
  File "/path/to/my/venv/lib/python3.5/site-packages/IPython/core/ultratb.py", line 358, in _fixed_getinnerframes
    records = fix_frame_records_filenames(inspect.getinnerframes(etb, context))
  File "/path/to/my/venv/lib/python3.5/inspect.py", line 1455, in getinnerframes
    frameinfo = (tb.tb_frame,) + getframeinfo(tb, context)
  File "/path/to/my/venv/lib/python3.5/inspect.py", line 1412, in getframeinfo
    filename = getsourcefile(frame) or getfile(frame)
  File "/path/to/my/venv/lib/python3.5/inspect.py", line 672, in getsourcefile
    if getattr(getmodule(object, filename), '__loader__', None) is not None:
  File "/path/to/my/venv/lib/python3.5/inspect.py", line 720, in getmodule
    os.path.realpath(f)] = module.__name__
AttributeError: module has no attribute '__name__'

This is quite noisy especially since the later two exceptions have nothing to do with my script. Can IPython do something to quiet this down? To be clear, AssertionError is not the problem. If I replace line 68 with 1/0, then you get `AttributeError: ‘ZeroDivisionError’ object has no attribute ‘render_traceback’. So it seems like IPython is making some assumptions that no longer hold in Python 3?

[chebee7i]

It looks like this may have been discussed on the Python mailing list too: https://mail.python.org/pipermail/python-list/2015-February/685695.html

They concluded it was a versioning issue, but I’m IPython 5.1.0 and I still have the issue.

[Carreau]

Should I keep these changes locally or should I wait for an updated version of ipython to be released, and do conda update IPython?

The fix will be included in next release. Usually last friday of the month, but next week is holliday so well likely soon. Once 7.10 is released you’ll be able to just update with conda.