Re: backend for matplotlib on NAS Lou (Thomas Caswell)
Just thought I report that I did get matplotlib working as desired on Lou. It turns out that using the version of matplotlib and ipython that's loaded by pkgsrc works (i.e. module load pkgsrc), if you set the backend to Qt4Agg or GtkAgg in your matplotlibrc. In my case I had to remove from my path the anaconda distribution that I had installed. I was also able to install yt using pip (with the --user argument so it installs under ~/.local).
Date: Tue, 06 Feb 2018 02:44:38 +0000
From: Thomas Caswell <[hidden email]>
To: "Slavin, Jonathan" <[hidden email]>
Cc: Matplotlib-users <[hidden email]>
Subject: Re: [Matplotlib-users] backend for matplotlib on NAS Lou
Content-Type: text/plain; charset="utf-8"
This should go either to anaconda support or to your local sysadmins.
It may also be worth trying to us `tkagg` which tends to bundled with
python and may have a higher chance of working.
On Mon, Feb 5, 2018 at 11:19 AM Slavin, Jonathan <[hidden email]>
> The platform is Suse Linux Enterprise Server 12.
> Also, I checked and there are no modules loaded:
> > module list
> No Modulefiles Currently Loaded.
> I also checked that I was launching the anaconda version of python/ipython.
> ?To be more explicit about the error, if I use in my matplotlibrc:
> ?backend : Qt5Agg
> backend.qt4 : PyQt4
> Then when I start up ipython with the --pylab argument, I get:
> [TerminalIPythonApp] WARNING | Eventloop or matplotlib integration failed.
> Is matplotlib installed?
> ImportError Traceback (most recent call last)
> in <lambda>(key)
> 196 shell = self.shell
> 197 if self.pylab:
> --> 198 enable = lambda key: shell.enable_pylab(key,
> 199 key = self.pylab
> 200 elif self.matplotlib:
> in <module>()
> 135 if QT_API == QT_API_PYQT5:
> 136 try:
> --> 137 from PyQt5 import QtCore, QtGui, QtWidgets
> 138 _getSaveFileName =
> 139 except ImportError:
> ImportError: /lib64/libpthread.so.0: version `GLIBC_2.12' not found
> (required by
> So I'm guessing that this has to do with the version of glibc installed
> rather than the missing gui toolkits as I had previously thought. It could
> be that loading some module might fix the problem, though I'm not sure if
> that's true or which one I'd need to load.
> Any ideas?
________________________________________________________ Jonathan D. Slavin Harvard-Smithsonian CfA [hidden email] 60 Garden Street, MS 83 phone: (617) 496-7981 Cambridge, MA 02138-1516 cell: (781) 363-0035 USA ________________________________________________________