ProPlot differentiates python, ipython, and jupyter XYZ sessions using the approach described in this stackoverflow answer. It activates %matplotlib inline for jupyter sessions and %matplotlib qt for terminal ipython sessions. However, the inline backend is only available for jupyter qtconsole and jupyter notebook, not for jupyter console. I opened a thread (jupyter/jupyter#490), but it may be virtually impossible to determine the type of jupyter frontend from the kernel itself at runtime.
The ipython_autoreload, ipython_autosave, and ipython_matplotlib functions (the latter sets up the backend), formerly part of a single nbsetup function, date from the earliest days of proplot when it was mixed in with some other utilities of mine. But now I'm not sure it makes sense to include them.
I think the next version of proplot should remove these functions, but keep the %config InlineBackend commands.
ProPlot differentiates
python,ipython, andjupyter XYZsessions using the approach described in this stackoverflow answer. It activates%matplotlib inlinefor jupyter sessions and%matplotlib qtfor terminal ipython sessions. However, the inline backend is only available forjupyter qtconsoleandjupyter notebook, not forjupyter console. I opened a thread (jupyter/jupyter#490), but it may be virtually impossible to determine the type of jupyter frontend from the kernel itself at runtime.The
ipython_autoreload,ipython_autosave, andipython_matplotlibfunctions (the latter sets up the backend), formerly part of a singlenbsetupfunction, date from the earliest days of proplot when it was mixed in with some other utilities of mine. But now I'm not sure it makes sense to include them.I think the next version of proplot should remove these functions, but keep the
%config InlineBackendcommands.