wxMPL status?

Hi all,

Anyone know what's up with wxMPL? It looks like Ken hasn't updated in soe
time, and it doesn't work with recent MPLs:

    from matplotlib.axes import _process_plot_var_args
ImportError: cannot import name _process_plot_var_args

We had a discussion about this a good while back:

https://sourceforge.net/p/matplotlib/mailman/message/29770257/

anything ever come of that???

-Chris

···

--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160222/80dfa024/attachment.html>

Hi Chris:

i have some things to do on it but Ken McIvor has left IIT some time ago
and I have not had a lot of time for software development.

If I get some time I hope to add the patches.

Carlo

···

On Mon, 22 Feb 2016, Chris Barker wrote:

Hi all,

Anyone know what's up with wxMPL? It looks like Ken hasn't updated in soe
time, and it doesn't work with recent MPLs:

   from matplotlib.axes import _process_plot_var_args
ImportError: cannot import name _process_plot_var_args

We had a discussion about this a good while back:

https://sourceforge.net/p/matplotlib/mailman/message/29770257/

anything ever come of that???

-Chris

--
Carlo U. Segre -- Duchossois Leadership Professor of Physics
Director, Center for Synchrotron Radiation Research and Instrumentation
Illinois Institute of Technology
Voice: 312.567.3498 Fax: 312.567.3494
segre at iit.edu http://phys.iit.edu/~segre segre at debian.org

HI Chris, Carlo, All,

Hi all,

Anyone know what's up with wxMPL? It looks like Ken hasn't updated in soe
time, and it doesn't work with recent MPLs:

    from matplotlib.axes import _process_plot_var_args
ImportError: cannot import name _process_plot_var_args

We had a discussion about this a good while back:

https://sourceforge.net/p/matplotlib/mailman/message/29770257/

anything ever come of that???

I guess not -- I haven't looked at this in a long time. I am still
maintaining wxmplot, and using it for quite a few apps, and I know at least
a few other people are using it too. Development (
https://github.com/newville/wxmplot) isn't fast, but it is not dead either.

My recollection was that there was a lot of overlap in functionality,
between wxmplot and wxmpl. For example, I believe both have a PlotPanel
class, derived from wx.Panel, and that although the initialization
arguments and methods names were pretty different, much of the real
functionality was similar. What uses of wxmpl would need to be ported
and/or translated (or some combination) to wxmplot to fit your needs?

But: I also have to say that the lack of wxPython (and matplotib+wx
backend) for Python3 is a major concern. If matplotlib's wx backend
supported Phoenix, I'd be more inclined to work on this. As it is, there
is not much evidence that investing significant time in wxPython-based
libraries is a good use of time.

If something like wxmplot.PlotPanel and ImagePanel (especially wrt giving
end users a configuration panel to adjust the plot / image) existed in
PyQt, I would seriously consider switching many of my GUI apps away from
wxPython right now. To be clear, II have ~25kLOC of wxPython code and half
a dozen non-trivial apps that I use at my lab daily.

So, while I'm sympathetic and willing to help some, I'm more concerned
about the very sad state of wxPython. If someone approached me about
"porting wxmplot to PyQt" (and replace the truly horrible matplotlib
defaults) I would be much more inclined to say yes.

--Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160223/d1ae84cf/attachment-0001.html>

···

On Mon, Feb 22, 2016 at 4:27 PM, Chris Barker <chris.barker at noaa.gov> wrote:

If I get some time I hope to add the patches.

That would be great -- we should make a gitHub project for it -- would you
like to do that, or should I?

or...

Development (https://github.com/newville/wxmplot) isn't fast, but it is
not dead either.

My recollection was that there was a lot of overlap in functionality,
between wxmplot and wxmpl.

What uses of wxmpl would need to be ported and/or translated (or some
combination) to wxmplot to fit your needs?

Boy, I have no idea! Back in teh day, I decided that wxMPL fit my needs a
bit better, but I can't recall why...IT is lighter weight, but I don't know
that the extra weight is a problem at all...

So our next step is going to be to take a look at wxmplot, and if it fits
the use case at hand, great! if not I guess we'll figure out if it's easier
to patch wxmplot of wxmpl to work for us.

Stay tuned...

But: I also have to say that the lack of wxPython (and matplotib+wx

backend) for Python3 is a major concern. If matplotlib's wx backend
supported Phoenix, I'd be more inclined to work on this. As it is, there
is not much evidence that investing significant time in wxPython-based
libraries is a good use of time.

Any idea what it would take for MPL to support Phoenix? Honestly, I haven't
given Phoenix a real try at all yet. I"ve got a handful of small apps (and
one biggish one) that are wx based, but not in active enough development to
want to deal with porting to py2 or Phoenix...

So, while I'm sympathetic and willing to help some, I'm more concerned

about the very sad state of wxPython.

yeah -- the irony is that Robin has been working on PySide for the last
while....

but while slow, wxPython still seems to have a good community, and Phoenix
does appear to be pretty close to operational....IT jsut needs some
prodding along, I suppose.

For my part, we are doing a lot more with Web apps, which I why I've had
little time for wx lately....

Thanks,

-CHB

···

On Mon, Feb 22, 2016 at 4:37 PM, Carlo Segre <segre at iit.edu> wrote:
On Tue, Feb 23, 2016 at 2:23 PM, Matt Newville <newville at cars.uchicago.edu> wrote:

--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160223/62786658/attachment.html>

Uhm, Phoenix should be supported:
https://github.com/matplotlib/matplotlib/pulls?utf8=✓&q=is%3Apr+phoenix
-- at least, experimentally given that at the time of these PRs, phoenix
wasn't finalized.

Ben Root
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160224/0386c95c/attachment.html>

···

On Tue, Feb 23, 2016 at 5:53 PM, Chris Barker <chris.barker at noaa.gov> wrote:

But: I also have to say that the lack of wxPython (and matplotib+wx

backend) for Python3 is a major concern. If matplotlib's wx backend
supported Phoenix, I'd be more inclined to work on this. As it is, there
is not much evidence that investing significant time in wxPython-based
libraries is a good use of time.

Any idea what it would take for MPL to support Phoenix? Honestly, I
haven't given Phoenix a real try at all yet. I"ve got a handful of small
apps (and one biggish one) that are wx based, but not in active enough
development to want to deal with porting to py2 or Phoenix...

Awesome!

I'll need to give it a try some day...

···

On Wed, Feb 24, 2016 at 7:26 AM, Benjamin Root <ben.v.root at gmail.com> wrote:

Uhm, Phoenix should be supported:
https://github.com/matplotlib/matplotlib/pulls?utf8=✓&q=is%3Apr+phoenix
-- at least, experimentally given that at the time of these PRs, phoenix
wasn't finalized.

--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160224/c68133cd/attachment.html>

HI Chris,

If I get some time I hope to add the patches.

That would be great -- we should make a gitHub project for it -- would you
like to do that, or should I?

or...

Development (https://github.com/newville/wxmplot) isn't fast, but it is
not dead either.

My recollection was that there was a lot of overlap in functionality,
between wxmplot and wxmpl.

What uses of wxmpl would need to be ported and/or translated (or some
combination) to wxmplot to fit your needs?

Boy, I have no idea! Back in teh day, I decided that wxMPL fit my needs a
bit better, but I can't recall why...IT is lighter weight, but I don't know
that the extra weight is a problem at all...

So our next step is going to be to take a look at wxmplot, and if it fits
the use case at hand, great! if not I guess we'll figure out if it's easier
to patch wxmplot of wxmpl to work for us.

Stay tuned...

OK. I think a transition from wxmpl to wxmplot might not be hard. If
there is anything that's missing in wxmplot that would make that transition
easier, let's add it.

But: I also have to say that the lack of wxPython (and matplotib+wx

backend) for Python3 is a major concern. If matplotlib's wx backend
supported Phoenix, I'd be more inclined to work on this. As it is, there
is not much evidence that investing significant time in wxPython-based
libraries is a good use of time.

Any idea what it would take for MPL to support Phoenix? Honestly, I
haven't given Phoenix a real try at all yet. I"ve got a handful of small
apps (and one biggish one) that are wx based, but not in active enough
development to want to deal with porting to py2 or Phoenix...

So, while I'm sympathetic and willing to help some, I'm more concerned

about the very sad state of wxPython.

yeah -- the irony is that Robin has been working on PySide for the last
while....

but while slow, wxPython still seems to have a good community, and Phoenix
does appear to be pretty close to operational....IT jsut needs some
prodding along, I suppose.

Actually, Benjamin Root is correct, and I should correct my earlier remarks.

Using matplotlib 1.5.1 and wxPython Phoenix 3.0.3.dev1839+4ecd949 works
well, and I've verified that almost all of the wxmplot examples work
without any modification at all. I've only tested with Python 2.7
(Python 2.7.11 from Anaconda 2.4.1 on Mac OS X to be precise). There are
a lot of differences between Phoenix and Classic, so wxmplot will need some
small modifications and version-checking code for everything to work.
There will no doubt be changes need for Python3, but I suspect not too
many.

This is really, really good news! Thanks very much matplotlib-dev team!

For my part, we are doing a lot more with Web apps, which I why I've had

little time for wx lately....

Yeah, that definitely has appeal. For most of the data collection,
visualization, and analysis applications I support, web interfaces just
don't give as intimate and immediate an experience as a desktop GUI. Both
are needed.

--Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160225/19bb9089/attachment-0001.html>

···

On Tue, Feb 23, 2016 at 4:53 PM, Chris Barker <chris.barker at noaa.gov> wrote:

On Mon, Feb 22, 2016 at 4:37 PM, Carlo Segre <segre at iit.edu> wrote:

On Tue, Feb 23, 2016 at 2:23 PM, Matt Newville <newville at cars.uchicago.edu> > wrote:

Matt et al,

WE probably shoudld jsut got to wxmplot -- but in the meantime, I created a
gitHub project for a fork of wxmpl:

https://github.com/NOAA-ORR-ERD/wxmpl

I've fixed the immediate mpl import issue, but now there are issues with a
newer wxPython -- at least with the demos. Hopefully I'll get to those
later today.

Carlo, let me know if you want write permissions on that repo -- or want to
set it up yourself somewhere else..

-CHB

···

On Thu, Feb 25, 2016 at 5:44 AM, Matt Newville <newville at cars.uchicago.edu> wrote:

HI Chris,

On Tue, Feb 23, 2016 at 4:53 PM, Chris Barker <chris.barker at noaa.gov> > wrote:

On Mon, Feb 22, 2016 at 4:37 PM, Carlo Segre <segre at iit.edu> wrote:

If I get some time I hope to add the patches.

That would be great -- we should make a gitHub project for it -- would
you like to do that, or should I?

or...

On Tue, Feb 23, 2016 at 2:23 PM, Matt Newville <newville at cars.uchicago.edu >> > wrote:

Development (https://github.com/newville/wxmplot) isn't fast, but it is
not dead either.

My recollection was that there was a lot of overlap in functionality,
between wxmplot and wxmpl.

What uses of wxmpl would need to be ported and/or translated (or some
combination) to wxmplot to fit your needs?

Boy, I have no idea! Back in teh day, I decided that wxMPL fit my needs a
bit better, but I can't recall why...IT is lighter weight, but I don't know
that the extra weight is a problem at all...

So our next step is going to be to take a look at wxmplot, and if it fits
the use case at hand, great! if not I guess we'll figure out if it's easier
to patch wxmplot of wxmpl to work for us.

Stay tuned...

OK. I think a transition from wxmpl to wxmplot might not be hard. If
there is anything that's missing in wxmplot that would make that transition
easier, let's add it.

But: I also have to say that the lack of wxPython (and matplotib+wx

backend) for Python3 is a major concern. If matplotlib's wx backend
supported Phoenix, I'd be more inclined to work on this. As it is, there
is not much evidence that investing significant time in wxPython-based
libraries is a good use of time.

Any idea what it would take for MPL to support Phoenix? Honestly, I
haven't given Phoenix a real try at all yet. I"ve got a handful of small
apps (and one biggish one) that are wx based, but not in active enough
development to want to deal with porting to py2 or Phoenix...

So, while I'm sympathetic and willing to help some, I'm more concerned

about the very sad state of wxPython.

yeah -- the irony is that Robin has been working on PySide for the last
while....

but while slow, wxPython still seems to have a good community, and
Phoenix does appear to be pretty close to operational....IT jsut needs some
prodding along, I suppose.

Actually, Benjamin Root is correct, and I should correct my earlier
remarks.

Using matplotlib 1.5.1 and wxPython Phoenix 3.0.3.dev1839+4ecd949 works
well, and I've verified that almost all of the wxmplot examples work
without any modification at all. I've only tested with Python 2.7
(Python 2.7.11 from Anaconda 2.4.1 on Mac OS X to be precise). There are
a lot of differences between Phoenix and Classic, so wxmplot will need some
small modifications and version-checking code for everything to work.
There will no doubt be changes need for Python3, but I suspect not too
many.

This is really, really good news! Thanks very much matplotlib-dev team!

For my part, we are doing a lot more with Web apps, which I why I've had

little time for wx lately....

Yeah, that definitely has appeal. For most of the data collection,
visualization, and analysis applications I support, web interfaces just
don't give as intimate and immediate an experience as a desktop GUI. Both
are needed.

--Matt

--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160225/0ae98e42/attachment.html>

Hi Matt,

In response to "If something like wxmplot.PlotPanel and ImagePanel
(especially wrt giving end users a configuration panel to adjust the plot /
image) existed in PyQt, I would seriously consider switching many of my GUI
apps away from wxPython right now," have you ever looked at the PyQtGraph
module? http://www.pyqtgraph.org/ I'm guessing it loses some functionality
you would consider important and I'd be interested, if you have any
thoughts on it, to know where it falls down as in the past we have gone for
wx for building GUIs and the discussion about moving to Qt/PySide
continually resurfaces,

thanks,
Gary

···

On 26 February 2016 at 00:44, Matt Newville <newville at cars.uchicago.edu> wrote:

HI Chris,

On Tue, Feb 23, 2016 at 4:53 PM, Chris Barker <chris.barker at noaa.gov> > wrote:

On Mon, Feb 22, 2016 at 4:37 PM, Carlo Segre <segre at iit.edu> wrote:

If I get some time I hope to add the patches.

That would be great -- we should make a gitHub project for it -- would
you like to do that, or should I?

or...

On Tue, Feb 23, 2016 at 2:23 PM, Matt Newville <newville at cars.uchicago.edu >> > wrote:

Development (https://github.com/newville/wxmplot) isn't fast, but it is
not dead either.

My recollection was that there was a lot of overlap in functionality,
between wxmplot and wxmpl.

What uses of wxmpl would need to be ported and/or translated (or some
combination) to wxmplot to fit your needs?

Boy, I have no idea! Back in teh day, I decided that wxMPL fit my needs a
bit better, but I can't recall why...IT is lighter weight, but I don't know
that the extra weight is a problem at all...

So our next step is going to be to take a look at wxmplot, and if it fits
the use case at hand, great! if not I guess we'll figure out if it's easier
to patch wxmplot of wxmpl to work for us.

Stay tuned...

OK. I think a transition from wxmpl to wxmplot might not be hard. If
there is anything that's missing in wxmplot that would make that transition
easier, let's add it.

But: I also have to say that the lack of wxPython (and matplotib+wx

backend) for Python3 is a major concern. If matplotlib's wx backend
supported Phoenix, I'd be more inclined to work on this. As it is, there
is not much evidence that investing significant time in wxPython-based
libraries is a good use of time.

Any idea what it would take for MPL to support Phoenix? Honestly, I
haven't given Phoenix a real try at all yet. I"ve got a handful of small
apps (and one biggish one) that are wx based, but not in active enough
development to want to deal with porting to py2 or Phoenix...

So, while I'm sympathetic and willing to help some, I'm more concerned

about the very sad state of wxPython.

yeah -- the irony is that Robin has been working on PySide for the last
while....

but while slow, wxPython still seems to have a good community, and
Phoenix does appear to be pretty close to operational....IT jsut needs some
prodding along, I suppose.

Actually, Benjamin Root is correct, and I should correct my earlier
remarks.

Using matplotlib 1.5.1 and wxPython Phoenix 3.0.3.dev1839+4ecd949 works
well, and I've verified that almost all of the wxmplot examples work
without any modification at all. I've only tested with Python 2.7
(Python 2.7.11 from Anaconda 2.4.1 on Mac OS X to be precise). There are
a lot of differences between Phoenix and Classic, so wxmplot will need some
small modifications and version-checking code for everything to work.
There will no doubt be changes need for Python3, but I suspect not too
many.

This is really, really good news! Thanks very much matplotlib-dev team!

For my part, we are doing a lot more with Web apps, which I why I've had

little time for wx lately....

Yeah, that definitely has appeal. For most of the data collection,
visualization, and analysis applications I support, web interfaces just
don't give as intimate and immediate an experience as a desktop GUI. Both
are needed.

--Matt

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160310/df0ab889/attachment-0001.html>

Hi Gary,

Hi Matt,

In response to "If something like wxmplot.PlotPanel and ImagePanel
(especially wrt giving end users a configuration panel to adjust the plot /
image) existed in PyQt, I would seriously consider switching many of my GUI
apps away from wxPython right now," have you ever looked at the PyQtGraph
module? http://www.pyqtgraph.org/

I have. I'm a happy user of a program that uses PyQtGraph. It seems
interesting, but very different from matplotlib (and so wxmplot). I have
a similar view of VisPy. I am happy with matplotlib.

For wxmplot I really wanted something to make interactive high quality 2D
line plots, including something like TeX support for text, and that also
does false-color image display (to allows relations between images and 2D
line plots). Matplotlib is excellent for these needs. PyQtGraph seems to
emphasize other things, including speed. Though I often hear complaints
about matplotlib being slow, I suspect this is due to confusion using
pylab.plot() with the plotting API. I can easily update line plots at 15
to 25 Hz with wxmplot. It's true that I do not use matplotlib for display
of video images -- I convert data from GigE and USB3 cameras directly to
wx.Images. PyQtGraph seems good for that as well, but that is separate
from matplotlib.

I'm guessing it loses some functionality you would consider important and

I'd be interested, if you have any thoughts on it, to know where it falls
down as in the past we have gone for wx for building GUIs and the
discussion about moving to Qt/PySide continually resurfaces,

Wxmplot provides a Plot-specific Panel with "plot" and "oplot" methods, as
well as live interaction for zooming, printing, copy-to-clipboard, and so
on. Of course, most of this comes from the matplotlib API. A
configuration form is readily available for end users to alter the plot
labels, colors, markers, etc for 2D line plots. See
http://newville.github.io/wxmplot/plotpanel.html#examples-and-screenshots
for an example. For false-color images, the user can change scales, color
tables, smoothing methods, and customize contour levels. In a sense,
wxmplot improves on matplotlib default Navigation Toolbars, which are
pretty limited.

I've been using wxPython for more than 10 years and have no complaints with
its functionality, only that development for Python3 has been very slow
(and so I'm very grateful that Phoenix is now supported with matplotlib
1.5). I don't see PyQt or PySide as actually being technically superior to
wx (except Python3 support), and find PyQt's use of the GPL annoying. None
of wxPython, PyQt, or PySide seems to have a large enough group of active
developers, and I would worry about stability and support of the GUI
library no matter which of these I was using.

Again, I could be persuaded to try to migrate wxmplot to PyQt/PySide, but
would definitely base that on matplotlib.

Cheers,

--Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160311/d81cc31c/attachment.html>

···

On Wed, Mar 9, 2016 at 9:08 PM, gary ruben <gary.ruben at gmail.com> wrote: