wxagg back-end bug on windows?

Hi all,

I'm having an odd issue with the wxAgg back-end:

windows XP
python 2.5.2 (from python.org)
wxPython 2.8.7.1 unicode (binary from wxPython.org)
MPL 0.91.2 (binary from MPl site)

when I run:
import matplotlib
matplotlib.use('wxagg')
import pylab

I get a popup dialog:

"This application failed to start because wxmsw26uh_vc.dll was not found"

It looks like it is looking for a wxPython2.6 dll, which it doesn't find, because I'm running wxPython2.8

I'm guessing this binary was compiled against wxPython2.6, but I thought the current wxAgg back-end didn't try to use the accelerated module for wxPython2.8.

Any ideas?

By the way, there are a number of other small bugs cropping up in the pylab window with wxagg too -- but I'll look at those once I solve this.

Is no one else using MPL with wxPython2.8?

-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@...259...

Chris Barker wrote:

Hi all,

I'm having an odd issue with the wxAgg back-end:

Update:

If I remove:

matplotlib/backends/_wxagg.pyd

The problem goes away.

It looks like that pyd is getting loaded even though I'm running wxPython2.8

However, now I get a non-valid png when I do savefig....

-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@...259...