matplotlib-users Mailing List for matplotlib (Page 1461)

Commented out line 43 in _matlab_helpers fix my issue. Is it because I don't 
have any window to destroy?
Here is small example (which creates problem without commenting line 43)
from matplotlib import use
use('GD')
from matplotlib.matlab import *
bar([0,1], [0,2])
savefig('test.png', dpi=100)
close('all')
bar([0,1], [1,1])
savefig('test1.png', dpi=100)
close('all')
********************New destroy function in _matlab_helpers (Need a fix if you 
have window to destroy 
*******************
 def destroy(num):
 if not GcfBase.has_fignum(num): return
 figwin = GcfBase.figs[num]
 oldQue = GcfBase._activeQue[:]
 GcfBase._activeQue = []
 for f in oldQue:
 if f != figwin: GcfBase._activeQue.append(f)
 del GcfBase.figs[num]
 #figwin.window.destroy()
 destroy = staticmethod(destroy)

http://biggles.sourceforge.net/libplot/
Just FYI.
njh

>>>>> "Samir" == Samir Patel <sp...@la...> writes:
Please email the list directly or CC it so others can benefit from the
discussion. For reason unclear to me, my posts to the list are held
up in some nebulous zone for many hours....
 Samir> I created image with GD library. I had 2 small issues: I
 Samir> add GDFONTPATH and while running from web server TTFQuery
 Samir> wanted to create a font
 Samir> "./usr/lib/python2.3/site-packages/ttfquery/font.cache" and
 Samir> it did not had permission. I simply created this file with
 Samir> write permission.
It looks like you are running in an environment where HOME is not set.
The TTFQuery file _scriptregistry.py first checks for the HOME
environment variable and tries to put the font cache there. If it
fails, it falls back on a python dir (which works well for linux and
win32 respectively). Also, make sure you are using version 0.2.6 of
TTFQuery.
So either 1) set HOME to point to where you want to font cache to go,
or 2) Edit _scriptregistry.py and manually set the registryFile
variable at the top of that script.
 Samir> Unfortunately I cannot put my stuff on public internet
 Samir> because I am working on my development machine which is
 Samir> inside my companies firewall and I have to create some good
 Samir> graphics forms for user to use it. I am planning to do both
 Samir> things withing a month or so. But I will be glad to
 Samir> transfer whatever knowledge and programs I have to start
 Samir> you on publishing graph on web.
I understand. If you have a publicly viewable screenshot that you can
share for the screenshot page, let me know. Otherwise, just pass on
what you learn about the mechanics of getting it up and running.
Thanks,
John Hunter

>>>>> "Samir" == Samir Patel <sp...@la...> writes:
 Samir> I am trying to save an image without showing it. Here is
 Samir> small program
There are a couple of ways to do it. It would help to know what
platform you are on. On linux/unix, there are the postscript and GD
backends which can generate images 'offline' w/o showing them. At
present, there is no way to generate a GTK image (GTK is the default
backend) w/o showing it. You should read the web pages
 http://matplotlib.sourceforge.net/installing.html
 http://matplotlib.sourceforge.net/backends.html
for more information on these issues.
Postscript is a high quality output that is more useful on linux/unix
platforms where there are usually viewers, converters and printers by
default. GD can be used to make PNGs and other image formats without
showing the image, but as far as I know there is no good windows
installer for gd module yet. I've spent some time working on it, and
have been corresponding with the author of gdmodule, and can probably
come up with one in the near future.
So that's the long answer. The short answer is -- if you are on
linux, install gd module following the instructions on the matplotlib
web site and use the GD or PS backend. If you are on windows, wait a
little bit and I'll see about getting the gd installer going, which is
something I've been meaning to do anyway.
Cheers,
John Hunter

PS solution works for me. One thing is that afm fonts are in gnome-print 
package (Took me some time to find where this fonts came from). Now I am 
trying to see whether I can make it work with Quixote (web server). I will 
try GD solution later on. Thanks for your suggestions.
- Samir

Samir,
Either call it with "python test.py -dGD" or use this code, with 2 new
lines at the beginning.
from matplotlib import use
use('GD')
from matplotlib.matlab import *
plot([1,2,3])
savefig('test.png')
----------------
Instructions for installing stuff for GD on the website. But if you just
need an image, do -dPS or use('PS') for postscript output.
	-C
 
--
Ask not what your computer can do for you; ask.... [ Uh-oh. ]

First of all, one of the easiest graph package yet fill with tons of 
capability and future potential. 
Now my issue:
I am trying to save an image without showing it. Here is small program
**************************************************************
from matplotlib.matlab import *
plot([1,2,3])
savefig('test.png')
#show()
***************************************************************
This does not create test.png file, but if I uncomment last line, it create 
test.png file. How can I create a test.png file without showing it? 

>>>>> "Charles" == Charles R Twardy <ct...@ma...> writes:
 Charles> That's installed now, but python figtext2.py -dGD makes
 Charles> it complain about GDFONTPATH even though
Mike Fletcher was kind enough to apply the ttfquery patch and release
TTFQuery-0.2.6 today, so GD users should grab that version from
http://sourceforge.net/projects/ttfquery to enable nonstandard true
type fonts.
JDH

>>>>> "Barry" == Barry Drake <bl...@ad...> writes:
 Barry> Thanks John. That fixed the hanging process. Now a
 Barry> message is coming back "none active" from the function:
 Barry> I haven't traced it back further yet.
Just kill the line -- that was a diagnostic debug message that should
have been removed before the release. 
Andrew Straw noted that a change I made in the axes module in 0.30
introduced a performance hit on his system. If you are experiencing
similar problems, I also fixed this. plots should load approx
twice as fast with the changes in CVS. 
JDH

Thanks John. That fixed the hanging process.
Now a message is coming back "none active" from the
function:
 def _get_active(self):
 if len(GcfBase._activeQue)==0:
 print 'None active'
 return None
 else: return self._activeQue[-1]
in the _matlab_helpers.py file. 
I haven't traced it back further yet.
Cheers.
Barry
--- John Hunter <jdh...@ac...> wrote:
> >>>>> "Barry" == Barry Drake <bl...@ad...>
> writes:
> 
> Barry> I'm observing some difference in behavior
> between the two
> Barry> versions. Running some example code in
> 0.29, after closing
> Barry> the plot windows, the python.exe process
> quits normally.
> Barry> The same example using 0.30 hangs the
> process and I have to
> Barry> kill it by hand. This occurs both at the
> command line and
> Barry> from within my editor (normally I execute
> from the editor).
> 
> Barry> Any ideas? Do I need to change some set
> up from when I was
> Barry> using 0.29?
> 
> Yes. I made several changes to this part of
> matplotlib to iron out
> some interactive bugs, and a new one crept in; I
> didn't notice it in
> my tests. The quick fix is to add the following
> code to
> matplotlib/backends/backend_gtk.py at line 773
> 
> if GcfGTK.get_num_figwins()==0 and
> ShowOn().is_mainloop_on():
> gtk.mainquit()
> 
> This is in the GcfGTK.destroy function, so the
> entire function should
> read
> 
> def destroy(num):
> if not GcfBase.has_fignum(num): return 
> figwin = GcfGTK.figs[num]
> figwin.figure.drawable= None
> GcfBase.destroy(num)
> if GcfGTK.get_num_figwins()==0 and
> ShowOn().is_mainloop_on():
> gtk.mainquit()
> destroy = staticmethod(destroy)
> 
> This should restore the old functionality -- let me
> know if you see
> anymore strangeness. I'll check the change into
> CVS.
> 
> [BTW, I posted the 0.30 announce to this mailing
> list this afternoon,
> but it didn't seem to make it. Hmmm.... Have I
> been moderated out of
> existence :-) ]
> 
> Thanks for the bug report, 
> John Hunter

Thanks to all (particularly Andrew and Charles) who contributed code
and bug reports leading to this release. Since my last post this
morning, I've cleared up several bugs in log scaling and interactive
mode. Definitely upgrade!
[Below is the general announcement]
matplotlib is a 2D plotting package for python with a matlab
compatible syntax and output tested under linux and windows platforms.
matplotlib-0.30 is available for download at
http://matplotlib.sourceforge.net, and has many new features since the
last major release.
Multiple outputs
 matplotlib now supports postscript and GD output, as well as the
 traditional GTK backend. The postscript backend goes a long way
 towards the goal of acheiving publication quality output. The GD
 backend allows you to use matplotlib even in environments with no X
 server, such as for a web application server serving dynamic charts.
Log scaling
 
 With the help of Andrew Straw, matplotlib now has log axis
 capabilities, with new commands semilogx, semilogy and loglog
 See http://matplotlib.sourceforge.net/screenshots.html#log_shot
Legends
 With the help of Charles R. Twardy, matplotlib now has a matlab
 compatible legend command. See
 http://matplotlib.sourceforge.net/screenshots.html#legend_demo
Numerous bug fixes and minor additions
 DPI parameter allows multiple output resolutions with correct
 scaling
 
 Several bug fixes in GTK interactive mode using
 examples/interactive2.py
 Multiple ways to specify colors, including matlab compatible format
 strings, RGB tuples, and html-style hex color strings
 Rewrite of line class for much greater compatibility with matlab
 handle graphics commands and flexibility in choosing line styles and
 markers
See http://matplotlib.sourceforge.net/screenshots.html for screenshots
and http://matplotlib.sourceforge.net/whats_new.html for more detailed
information on what's new.
John Hunter

[This didn't make it through when I sent it this afternoon. Not sure
why; sorry if you get a duplicate. ]
matplotlib-0.30 is available for download at
http://matplotlib.sourceforge.net, and has many new features since the
last major release.
Multiple outputs
 matplotlib now supports postscript and GD output, as well as the
 traditional GTK backend. The postscript backend goes a long way
 towards the goal of acheiving publication quality output. The GD
 backend allows you to use matplotlib even in environments with no X
 server, such as for a web application server serving dynamic charts.
Log scaling
 
 With the help of Andrew Straw, matplotlib now has log axis
 capabilities, with new commands semilogx, semilogy and loglog
 See http://matplotlib.sourceforge.net/screenshots.html#log_shot
Legends
 With the help of Charles R. Twardy, matplotlib now has a matlab
 compatible legend command. See
 http://matplotlib.sourceforge.net/screenshots.html#legend_demo
Numerous bug fixes and minor additions
 DPI parameter allows multiple output resolutions with correct
 scaling
 
 Several bug fixes in GTK interactive mode using
 examples/interactive2.py
 Multiple ways to specify colors, including matlab compatible format
 strings, RGB tuples, and html-style hex color strings
 Rewrite of line class for much greater compatibility with matlab
 handle graphics commands and flexibility in choosing line styles and
 markers
See http://matplotlib.sourceforge.net/screenshots.html for screenshots
and http://matplotlib.sourceforge.net/whats_new.html for more detailed
information on what's new.
John Hunter
Hi Nigel,
There has been a discussion on the scipy mailing list about a desire
to include your matfile in the scipy distribution. There is a
problem, however, in that scipy is distributed under a BSD compatible
license and the maintainers are hesitant to put GPL'd code in for fear
that it would hinder adoption by the business community. Would you be
willing to release a version of your matfile under a BSD/Python
compatible license for inclusion in scipy? There is currently support
for matfile version4 , but version 5 would be wonderful.
BTW, I have also done some work in matlab/python compatibility in a
plotting library I developed http://matplotlib.sourceforge.net.
Thought you might be interested.
John Hunter

>>>>> "Barry" == Barry Drake <bl...@ad...> writes:
 Barry> I'm observing some difference in behavior between the two
 Barry> versions. Running some example code in 0.29, after closing
 Barry> the plot windows, the python.exe process quits normally.
 Barry> The same example using 0.30 hangs the process and I have to
 Barry> kill it by hand. This occurs both at the command line and
 Barry> from within my editor (normally I execute from the editor).
 Barry> Any ideas? Do I need to change some set up from when I was
 Barry> using 0.29?
Yes. I made several changes to this part of matplotlib to iron out
some interactive bugs, and a new one crept in; I didn't notice it in
my tests. The quick fix is to add the following code to
matplotlib/backends/backend_gtk.py at line 773
 if GcfGTK.get_num_figwins()==0 and ShowOn().is_mainloop_on():
 gtk.mainquit()
This is in the GcfGTK.destroy function, so the entire function should
read
 def destroy(num):
 if not GcfBase.has_fignum(num): return 
 figwin = GcfGTK.figs[num]
 figwin.figure.drawable= None
 GcfBase.destroy(num)
 if GcfGTK.get_num_figwins()==0 and ShowOn().is_mainloop_on():
 gtk.mainquit()
 destroy = staticmethod(destroy)
This should restore the old functionality -- let me know if you see
anymore strangeness. I'll check the change into CVS.
[BTW, I posted the 0.30 announce to this mailing list this afternoon,
but it didn't seem to make it. Hmmm.... Have I been moderated out of
existence :-) ]
Thanks for the bug report, 
John Hunter

I installed the latest release 0.30 replacing 0.29,
after uninstalling 0.29.
I'm observing some difference in behavior between the
two versions. Running some example code in 0.29,
after closing the plot windows, the python.exe process
quits normally. The same example using 0.30 hangs the
process and I have to kill it by hand. This occurs
both at the command line and from within my editor
(normally I execute from the editor).
I'm using Windows XP pro and UltraEdit.
Any ideas? Do I need to change some set up from when
I was using 0.29?
Thanks.
Barry
--- John Hunter <jdh...@ac...> wrote:
> 
> matplotlib is a 2D plotting package for python with
> a matlab
> compatible syntax and output tested under linux and
> windows platforms.
> 
> matplotlib-0.30 is available for download at
> http://matplotlib.sourceforge.net, and has many new
> features since the
> last major release.
> 
> Multiple outputs
> 
> matplotlib now supports postscript and GD output,
> as well as the
> traditional GTK backend. The postscript backend
> goes a long way
> towards the goal of acheiving publication quality
> output. The GD
> backend allows you to use matplotlib even in
> environments with no X
> server, such as for a web application server
> serving dynamic charts.
> 
> Log scaling
> 
> With the help of Andrew Straw, matplotlib now has
> log axis
> capabilities, with new commands semilogx,
> semilogy and loglog
> See
>
http://matplotlib.sourceforge.net/screenshots.html#log_shot
> 
> Legends
> 
> With the help of Charles R. Twardy, matplotlib now
> has a matlab
> compatible legend command. See
> 
>
http://matplotlib.sourceforge.net/screenshots.html#legend_demo
> 
> Numerous bug fixes and minor additions
> 
> DPI parameter allows multiple output resolutions
> with correct
> scaling
> 
> Several bug fixes in GTK interactive mode using
> examples/interactive2.py
> 
> Multiple ways to specify colors, including matlab
> compatible format
> strings, RGB tuples, and html-style hex color
> strings
> 
> Rewrite of line class for much greater
> compatibility with matlab
> handle graphics commands and flexibility in
> choosing line styles and
> markers
> 
> See
> http://matplotlib.sourceforge.net/screenshots.html
> for screenshots
> and http://matplotlib.sourceforge.net/whats_new.html
> for more detailed
> information on what's new.
> 
> John Hunter
> _______________________________________________
> SciPy-user mailing list
> Sci...@sc...
> http://www.scipy.net/mailman/listinfo/scipy-user

>>>>> "Andrew" == Andrew Straw <as...@in...> writes:
 Andrew> Hi All, OK, I've got tick/grid positioning and labeling
 Andrew> working now, too.
Thanks! I have incorporated your changes into CVS, and added some new
functions to matlab.py (semilogx, semilogy, loglog). I have done some
additional work to make the tick labels and automatic view lim behave
properly (eg, labeling only the decades, which becomes important for
data with a wide range of decades, and doing a better job of
autosetting the view lim for log scaling). There is still some work
to be done, for example to properly handle the case where the axis lim
are set by the user, and where the scale is changed interactively, but
I thought the existing code was useful enough to do a new release of
the sourceforge site, 0.29.2.
One the remaining issues are cleared up, I want to do a release to the
wider python community, so please report any bugs.
Thanks again, Andrew. Keep them coming.
JDH
Some example code :
from matplotlib.matlab import *
dt = 0.01
t = arange(dt, 20.0, dt)
subplot(311)
semilogy(t, exp(-t/5.0))
subplot(312)
semilogx(t, sin(2*pi*t))
subplot(313)
loglog(t, exp(-t/10.0))
show()

Hi All,
OK, I've got tick/grid positioning and labeling working now, too.
There's a strange clipping issue when a gridline should be drawn near 
the border of the axes -- the gridline and tick disapper, but the 
ticklabel remains.
It looks like matplotlib is getting quite close to log plots!
Cheers!
Andrew

I've done a partial implementation of log plots. The data is transformed 
and shows up, but I haven't yet implemented smart tick locations or tick 
labels. (And I haven't checked the auto view setting abilities.)
I don't know how others feel, but I prefer my tick labels on log plots 
to say "10" and "100" rather than "10^1" and "10^2", so I'd vote for 
this as the default behavior for matplotlib. (At least for values < 1000 
or so.) I mention this because matlab seems to work the other way.
So, here's a patch to the various bits I changed, and a simple example 
that makes two plots.
John, you're welcome to include this in matplotlib as long as matplotlib 
remains under the current license.
Cheers!
Andrew

I just uploaded a new release to http://matplotlib.sourceforge.net.
 * Several bug fixes in the GTK backend which affected interactive
 mode and figure resizing. See examples/interactive2.py in the new
 src release.
 * The legend command from CVS has been added. See
 examples/legend_demo.py
 * Some bugs regarding alternate ways of specifying colors have been
 ironed out (you can now use hex strings or 0-1 RGB tuples anywhere
 a color format string is supported ). See examples/color_demo.py
Let me know of any problems you find.
John

>>>>> "Barry" == Barry Drake <bl...@ad...> writes:
 Barry> Update on the interactive mode: I found the interactive2.py
 Barry> on the website and tried that rather than the
 Barry> interactive.py that was included with the .29 dist. That
 Barry> worked. However,
 Barry> 1. it can't find ShowOn (NameError) so I just typed show()
 Barry> at the command prompt
I made several bug fixes that have restored interactive2.py
functionality. When I added support for other outputs (PS and GD) a
few bugs crept into the GTK output that I was unaware of, and tracking
down your problems made them clear to me. 
I just uploaded a new file release to the sourceforge site that
reflects these changes to the GTK backend and interactive2.py, as well
as the new legend command. The version is 0.29.1, so you should grab
a copy and give it a try. Note you'll need the src distribution (zip
or tar.gz) to get the new examples/interactive2.py file.
 Barry> 2. and it doesn't exit using ctrl-z <enter> ; I used the
 Barry> close box.
This one is still on the TODO list.
Hope this helps,
John Hunter

>>>>> "Andrew" == Andrew Straw <as...@in...> writes:
 Andrew> Sorry to ask for the Nth time, but as essentially all of
 Andrew> my plots require at least one log10 axis and as matplotlib
 Andrew> looks better and better, I'm wondering about the status of
 Andrew> log axes.
No need to apologize, pestering is a good thing since it motivates me
to do the things I already want to do when I know people want them.
 Andrew> This has even brought me to the point of delving into the
 Andrew> innards of matplotlib just to see how easy (or hard) it
 Andrew> would be. So far, it looks possibly like overriding the
 Andrew> various Artist.transform_*() methods and some additions to
 Andrew> axes.py. Is this the case? Would I be duplicating effort
 Andrew> if I jumped in at this point? I can't tell at this point
 Andrew> how much work it looks to be -- any estimation?
This is certainly the core change. Other considerations are to get
tick labels to work properly (using exponential or some suitable
notation) and to get the tick locs right (choose them on the decades,
probably using some preset decade choices for the most common use
cases). And the changes need to be consistent with handle graphics,
so that the user can say, for example
 set(gca(), 'xscale', 'log') or
 set(gca(), 'xscale', 'linear) 
and have the desired effect. The latter will happen automagically if
the Axes class defines a set_xscale and set_yscale method expecting
the string arg, which the then forwards the calls to a set_scale
method of the Axes._xaxis or Axes._yaxis instances.
I have been busier than anticipated over the last week so haven't been
able to address this issue as I had hoped, but have been tinkering
with it and thinking about it. If you look at CVS axes class, you'll
see the results of my tickering in the _scale, _scalemap, _scalefunc
attributes of the Axis class. I'm not at all convinced this is the
right design, though. One thing to consider is to factor the tick
loc-ing and labeling into a separate class to clean up the Axis
design.
As far as your helping, that would be great. As far as how much time
it would take, I think it would take me anywhere from half a day to
two days to get it just right, but I'm inclined to the lower
estimates. Let me know how you want to proceed: I can envision
anything from you making the required changes and checking them into
CVS, to us collaborating on the design and implementation, to me just
getting off my ass and doing it. I would certainly welcome some input
from you, and know from the quality of your work on vision egg that it
would improve matplotlib. Which given your impending move to the
Dickinson lab, might be a good thing for you too :-)
 Andrew> However, I think "ticks = asarray(ticks)" would be
 Andrew> cleaner, and probably little faster, too.
Right, I wrote some of the code a long time ago and would do this
differently now. My original thought was that in many of the use
cases the sequences would already be arrays and the try/except thing
would avoid a performance hit of creating a new array, but have since
learned that this is the purpose of asarray. If you decide to do the
log scaling thing, feel free to make these kinds of changes as you
go. The examples dir currently serves as my poor-man's unit testing
framework so you can validate your changes against them. 
Note that I made several minor changes to the code last night so be
sure to grab the latest CVS if you want to do any development.
John

Sorry to ask for the Nth time, but as essentially all of my plots 
require at least one log10 axis and as matplotlib looks better and 
better, I'm wondering about the status of log axes.
This has even brought me to the point of delving into the innards of 
matplotlib just to see how easy (or hard) it would be. So far, it looks 
possibly like overriding the various Artist.transform_*() methods and 
some additions to axes.py. Is this the case? Would I be duplicating 
effort if I jumped in at this point? I can't tell at this point how 
much work it looks to be -- any estimation?
As a mostly-trivial side-note, while looking through axes.py, I saw a 
few lines like:
 try: ticks.shape
 except AttributeError: ticks = array(ticks)
However, I think "ticks = asarray(ticks)" would be cleaner, and probably 
 little faster, too.
Cheers!
Andrew

Update on the interactive mode:
I found the interactive2.py on the website and tried
that rather than the interactive.py that was included
with the .29 dist. That worked. However, 
1. it can't find ShowOn (NameError) so I just typed
show() at the command prompt 
2. and it doesn't exit using ctrl-z <enter> ; I used
the close box.
Barry
--- John Hunter <jdh...@ac...> wrote:
> >>>>> "Barry" == Barry Drake <bl...@ad...>
> writes:
> 
> Barry> I've searched the files for this name,
> Line2D_Dispatcher,
> Barry> and can't find it. Is something missing
> from my
> Barry> installation?
> 
> This looks like a version conflict in matplotlib. 
> The dispatcher
> thing is from an older version and is no longer
> used, and the
> _simple_demo.py code has been removed as well. I
> suggest you remove
> the C:\Python23\Lib\site-packages\matplotlib dir
> entirely and
> reinstall version 0.29 from the matplotlib
> sourceforge site.
> 
> Then you should be able to run the examples in the
> examples dir of the
> src distribution without problems.
> 
> Let me know how it goes,
> John Hunter
> 
> 
>
-------------------------------------------------------
> This SF.net email sponsored by: Enterprise Linux
> Forum Conference & Expo
> The Event For Linux Datacenter Solutions &
> Strategies in The Enterprise 
> Linux in the Boardroom; in the Front Office; & in
> the Server Room 
> http://www.enterpriselinuxforum.com
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
>
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I am using the 0.29 version of matplotlib. I switched
to running the examples from the tutorial and things
are working great.
You verified what I thought, that _simple_demo.py was
from an earlier version.
I haven't been able to use the package interactively
yet. At a command prompt, I was able to run the
thread test from the website though. I'll mainly be
using matplotlib statically anyway.
As a long time Matlab user, I was very happy to find
this package!
Thanks for your quick response.
Barry
--- John Hunter <jdh...@ac...> wrote:
> >>>>> "Barry" == Barry Drake <bl...@ad...>
> writes:
> 
> Barry> I've searched the files for this name,
> Line2D_Dispatcher,
> Barry> and can't find it. Is something missing
> from my
> Barry> installation?
> 
> This looks like a version conflict in matplotlib. 
> The dispatcher
> thing is from an older version and is no longer
> used, and the
> _simple_demo.py code has been removed as well. I
> suggest you remove
> the C:\Python23\Lib\site-packages\matplotlib dir
> entirely and
> reinstall version 0.29 from the matplotlib
> sourceforge site.
> 
> Then you should be able to run the examples in the
> examples dir of the
> src distribution without problems.
> 
> Let me know how it goes,
> John Hunter

>>>>> "Barry" == Barry Drake <bl...@ad...> writes:
 Barry> I've searched the files for this name, Line2D_Dispatcher,
 Barry> and can't find it. Is something missing from my
 Barry> installation?
This looks like a version conflict in matplotlib. The dispatcher
thing is from an older version and is no longer used, and the
_simple_demo.py code has been removed as well. I suggest you remove
the C:\Python23\Lib\site-packages\matplotlib dir entirely and
reinstall version 0.29 from the matplotlib sourceforge site.
Then you should be able to run the examples in the examples dir of the
src distribution without problems.
Let me know how it goes,
John Hunter

I'm running Python 2.3 on win XPro. When I try to run
the simple example code I get the following error
output:
Traceback (most recent call last):
 File
"C:\Python23\Lib\site-packages\matplotlib\_simple_demo.py",
line 6, in ?
 from matplotlib.figure import Figure, Subplot
 File
"C:\Python23\Lib\site-packages\matplotlib\figure.py",
line 19, in ?
 from lines import Line2D_Dispatcher, SolidLine2D,
\
ImportError: cannot import name Line2D_Dispatcher
I've searched the files for this name,
Line2D_Dispatcher, and can't find it. Is something
missing from my installation?
Thanks.
Barry Drake