[Matplotlib-users] backend for matplotlib on NAS Lou

[Slavin, Jonathan]

​Jerzy,

It's physics - astrophysics.  In any case, since it's a NASA system I
cannot load it up with a lot of software, though I did install the anaconda
distribution as I mentioned. The issue is that the anaconda system does not
include the toolkits needed to use the backends that display plots in a
separate window.  These include pygtk, PyQt5, wxpython, etc. and need to be
installed for plotting via pyplot.show().  I could still use a jupyter
notebook​

​though for me that's less desirable.

Jon
​

>
> Date: Fri, 2 Feb 2018 22:23:18 +0100
> From: Jerzy Karczmarczuk <jerzy.karczmarczuk at unicaen.fr>
> To: matplotlib-users at python.org
> Subject: Re: [Matplotlib-users] backend for matplotlib on NAS Lou
> Message-ID: <10e2370c-451d-57a5-ab6d-dcdaa43a8a03 at unicaen.fr>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Le 02/02/2018 ? 21:39, Slavin, Jonathan a ?crit?:
>
> > Qt5Agg leads to an error from libpthread about the GLIBC version.? Qt4
> > fails with "No module named PyQt4".? Anyway, does anyone have a
> > solution to this?
> >
> > Of course, I could ask this of the NAS folks, but I thought it was
> > likely that someone on this list had dealt with this problem.
>
> Since you are a professional in astro-whatever, I *might* susepct that
> you loaded in your computer a good deal of specific software.
> I did that once, when I taught something the local folks name
> "informatique g?ographique".? Not knowing what I would really use, I fed
> the beast with at least 5 different GIS, and some other stuff, some of
> which came with their private copies of QT and PyQT. And there were
> conflicts...
> A thorough cleaning, elimination of double packages, isolating the
> environments, and ensuring that when I use Anaconda Matplotlib packages,
> its support is searched for first, really helped, not only me and my
> students, but some friends (local physicists) as well. No guarantee,
> though...
>
> Best regards
>
> Jerzy Karczmarczuk
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.python.org/pipermail/matplotlib-users/
> attachments/20180202/86375964/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 03 Feb 2018 07:00:29 +0200
> From: Rory Yorke <rory.yorke at gmail.com>
> To: matplotlib-users <matplotlib-users at python.org>
> Subject: Re: [Matplotlib-users] Replacing deprecated use of
>         pyplot.subplot
> Message-ID: <87h8qyu0pe.fsf at gmail.com>
> Content-Type: text/plain
>
> Hi Paul,
>
> Paul Hobson <pmhobson at gmail.com> writes:
> >> In general, especially for library code, you should avoid relying on the
> >> pyplot state machine.
>
> OK, thanks.  Eric said much the same in his reply.
>
> Thanks for the example code, that helps.  It seems like the recommended
> overall approach is "if axes are provided, used them, else create new ones;
> return the axes used".
>
> For now we'll use the approach I've implemented, perhaps with Eric's
> suggested improvement.  I'll propose creating a new suite of plot
> functions (there are several specialized plots we do: Bode, Nichols,
> etc.) that adopt the no-state-machine approach.
>
> Thanks, both to you and Eric.
>
> Regards,
>
> Rory
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Matplotlib-users mailing list
> Matplotlib-users at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-users
>
>
> ------------------------------
>
> End of Matplotlib-users Digest, Vol 31, Issue 1
> ***********************************************
>



-- 
________________________________________________________
Jonathan D. Slavin                 Harvard-Smithsonian CfA
jslavin at cfa.harvard.edu       60 Garden Street, MS 83
phone: (617) 496-7981       Cambridge, MA 02138-1516
cell: (781) 363-0035             USA
________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-users/attachments/20180204/8867b8d5/attachment.html>