[yt-dev] Fwd: [yt_analysis/yt] show() failure due to IPython API changes (issue #428)
Matthew Turk
matthewturk at gmail.com
Tue Sep 25 12:53:55 PDT 2012
Can somebody address this? I'd like to ensure we can continue keeping
up with IPython (especially since a bunch of us are investing in it
quite heavily for our own workflows) but I can't add this to my queue
this at the moment. I think the best way to do this is probably to
add an IPython compat layer to yt/utilities/ that handles higher-level
functionality, since we use relatively little of the IPython API.
-Matt
---------- Forwarded message ----------
From: Anthony Scopatz <issues-reply at bitbucket.org>
Date: Tue, Sep 25, 2012 at 3:49 PM
Subject: [yt_analysis/yt] show() failure due to IPython API changes (issue #428)
To: matthewturk at gmail.com
--- you can reply above this line ---
New issue 428: show() failure due to IPython API changes
https://bitbucket.org/yt_analysis/yt/issue/428/show-failure-due-to-ipython-api-changes
Anthony Scopatz:
Reporting that the Plot.show() method seems to fail on IPython
0.14-dev because of an API change. The send_figure function is no
longer where yt thinks it is.
{{{python
ImportError Traceback (most recent call last)
<ipython-input-2-4804b2a8abc5> in <module>()
4 p.annotate_flash_ray_data(pf, 'jet', 10)
5 p.annotate_timestamp(0.2/z, 0.2/z, pf, units="days", size=24)
----> 6 p.show()
/home/scopatz/.local/lib/python2.7/site-packages/yt-3.0dev-py2.7-linux-x86_64.egg/yt/visualization/plot_window.pyc
in show(self)
788 """
789 if "__IPYTHON__" in dir(__builtin__):
--> 790 self._send_zmq()
791 else:
792 raise YTNotInsideNotebook
/home/scopatz/.local/lib/python2.7/site-packages/yt-3.0dev-py2.7-linux-x86_64.egg/yt/visualization/plot_window.pyc
in _send_zmq(self)
763
764 def _send_zmq(self):
--> 765 from IPython.zmq.pylab.backend_inline import \
766 send_figure
767 for k, v in sorted(self.plots.iteritems()):
ImportError: cannot import name send_figure
}}}
--
This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.
More information about the yt-dev
mailing list