These are chat archives for ipython/ipython

8th
Sep 2015
Lucy Park
@e9t
Sep 08 2015 14:13
Anybody here? I'm using startup scripts with my IPython and have included %matplotlib inline to include graphics within my notebooks. But that line also runs with my IPython shell, which is something I don't want. How can I run %matplotlib inline only for IPython notebooks, and not for the shell in my startup scripts?
Lucy Park
@e9t
Sep 08 2015 14:58
Well, just made a work around in the mean while:
from IPython import get_ipython

if 'terminal' not in str(get_ipython()):
    %matplotlib inline
    %config InlineBackend.figure_format = ‘retina’
Jonathan Frederic
@jdfreder
Sep 08 2015 15:05
@e9t your workaround is probably the best solution for now. The kernel intentionally is unaware of the type of client connected to it.
Lucy Park
@e9t
Sep 08 2015 15:06
Great. Thanks!
Sylvain Corlay
@SylvainCorlay
Sep 08 2015 16:32
@minrk , Jason told me that you had a good reason to prefer distutils over setuptools for develop mode install.
I am having an issue with that at the moment and was wondering if it is the same.
custom version of build_py is not used in develop mode.
is it the problem you were having?
Min RK
@minrk
Sep 08 2015 16:38
I use pip install -e, which is the same as setuptools develop. It has problems, though.
Sylvain Corlay
@SylvainCorlay
Sep 08 2015 17:01
thanks
Kyle Kelley
@rgbkrk
Sep 08 2015 17:30
ipython is not very happy in a docker container anymore, even when launched with -it (sets up the container session with an interactive terminal):
In [3]:
Do you really want to exit ([y]/n)? y

^C

^C^C^C^C
^C
^C
^C
^C^C^C^C^C no seriously stop it ^C^C^C^C
That may be the additional zmq stuff going on with a dask distributed client though....
yup, that's it
Min RK
@minrk
Sep 08 2015 17:39
Do you think it's zmq, not signal catching in dask.distributed?
Kyle Kelley
@rgbkrk
Sep 08 2015 17:42
This locks up when an initial dask.distributed.Client couldn't connect
I killed that in In[2]
(DNS did not resolve)
Jason Grout
@jasongrout
Sep 08 2015 17:42
try doing "sudo no seriously stop it"
Kyle Kelley
@rgbkrk
Sep 08 2015 17:43
Ha
I nuked it from a separate terminal