matplotlib-users Mailing List for matplotlib (Page 5)

>>>>> "Todd" == Todd Miller <jm...@st...> writes:

    Todd> This may be more FUD than fact but... my recollection of
    Todd> this is that different versions of Tcl/Tk are used between
    Todd> Python-2.2 and Python-2.3, I believe 8.3 and 8.4
    Todd> respectively.  Our process for creating the windows binaries
    Todd> for maplotlib requires a copy of the Tcl/Tk headers.  The
    Todd> last time I tried to make a 2.2 version of matplotlib, I was
    Todd> able to get matplotlib to compile and link using different
    Todd> Tcl/Tk headers (8.3), and matplotlib imported successfully,
    Todd> but it was unstable.  So, my impression is that the problem
    Todd> boils down to getting Python-2.2 specific support for Tcl/Tk
    Todd> into win32_static.

Not FUD, fact:-)

With this clarification I was able to get 2.2 compiled properly with
tkagg and the other backends.  I uploaded it to the SF site.  This is
the Numeric build.

Todd, I don't want to get into a situation where we are building
Numeric + numarray 0.9 + numarray 1.0 cross python 2.2, python2.3 and
python2.4 (that would be 9 win32 builds!) but we may want to consider
doing python2.2 builds for milestone releases, eg every couple/few
months.  I uploaded a new win32 static to the sf site which includes
the tcl83 and tcl84 headers and updated setupext.py in CVS to use
them.

JDH

As you said, my packages were messed up.
After removing site-package and build, the problem was gone.
I have no idea about what happened, but thanks for your advice.

Daehyok Shin

On Wed, 2004-08-11 at 09:19, John Hunter wrote:
> That is very bizarre.  Take a look at
> site-packages/matplotlib/patches.py - you should have set_antialiased
> defined on line 70 in the Patches class.  Rectangle should derive from
> Patches on line 119.
> 
> It looks a little like your build is messed up in some way I don't
> understand.  You may want to try removing matplotlib from your
> site-packages dir, removing 'build' from your matplotlib src tree, adn
> doing a clean install.

On Wed, 2004-08-11 at 09:07, John Hunter wrote:
> >>>>> "Gary" == Gary Strangman <st...@nm...> writes:
> 
> 
>     Gary> I recently found matplotlib and think it's _exactly_ what
>     Gary> the python environment needs from the scientific perspective
>     Gary> ... interactive plotting as good as (or better than)
>     Gary> Matlab's, that also makes it easy for Matlab users to be
>     Gary> converted. ;-) I'm very impressed in the
>     Gary> effort-to-date. Unfortunately, other software I use forces
>     Gary> me to stay with python2.2, and I'm having tremendous trouble
>     Gary> building matplotlib for win32. Might someone have a pointer
>     Gary> to a self-installing executable for matplotlib compiled
>     Gary> against python2.2 that is a more recent version than
>     Gary> v0.54.1??
> 
>     Gary> Thanks! And cheers to all the developers of this package.
> 
> Hi Gary - thanks for the kind words (and thanks for the stats module
> as well, which I've been using intermittently for years).
> 
> There is a bug in the _tkagg extension in the python2.2 build which
> has never been tracked down and fixed, which is why we stopped
> releasing it.  You get a missing DLL error when you try and load it.
> I opened _tkagg.pyd in dependency walker, and the DLL is one of the
> Visual Studio .NET dlls - though sometimes dependency walker fives
> false alarms.
> 
> As I write this, it occurs to me the problem that arose in 2.2 may
> have been coincident in my changing build environments (I don't know
> if Todd experienced a similar problem with his numarray builds with
> tkagg and python2.2, but I think he may have ...).

This may be more FUD than fact but... my recollection of this is that
different versions of Tcl/Tk are used between Python-2.2 and
Python-2.3,  I believe 8.3 and 8.4 respectively.  Our process for
creating the windows binaries for maplotlib requires a copy of the
Tcl/Tk headers.  The last time I tried to make a 2.2 version of
matplotlib,  I was able to get matplotlib to compile and link using
different Tcl/Tk headers (8.3), and matplotlib imported successfully, 
but it was unstable.  So,  my impression is that the problem boils down
to getting Python-2.2 specific support for Tcl/Tk into win32_static. 

Regards,
Todd

>>>>> "Ryugan" == Ryugan Mizuta <ryu...@sb...> writes:

    Ryugan> I'm a newbie and am trying to create a financial chart
    Ryugan> that converts or plots a tick data to any time frame
    Ryugan> (ex. daily, intraday and etc...).  I'm also using data
    Ryugan> that is written in a text file.  I only see an example
    Ryugan> that uses Yahoo data.

    Ryugan> Could anybody help me on how I can do this?

The examples finance_work on the web site
http://matplotlib.sourceforge.net/screenshots.html#finance_work2 loads
financial data from a CSV file.  It uses a function load_quotes
defined in the helper.py module

  http://matplotlib.sourceforge.net/screenshots/finance_work2.py
  http://matplotlib.sourceforge.net/screenshots/helpers.py

The data files for this example are found in 

  http://matplotlib.sourceforge.net/screenshots/data/

The downside is that this is a fairly sophisticated example that may
not be that easy to parse if you are getting started with
python/matplotlib, so hopefully someone on this list can provide a
simpler one for you.

Hope this helps,
John

>>>>> "Shin" == Shin  <sd...@em...> writes:

    Shin> My first trial produced the following error message.  What
    Shin> problem do you think is in my installation?  I am using
    Shin> GtkAgg backend for matplotlib 0.6.1 version in Mandrake 10
    Shin> and python 2.3.3.  Thanks.

That is very bizarre.  Take a look at
site-packages/matplotlib/patches.py - you should have set_antialiased
defined on line 70 in the Patches class.  Rectangle should derive from
Patches on line 119.

It looks a little like your build is messed up in some way I don't
understand.  You may want to try removing matplotlib from your
site-packages dir, removing 'build' from your matplotlib src tree, adn
doing a clean install.

For the record, I did a clean install of 0.61.0 on a linux machine I
don't normally develop on and ran your example without problems

    >>> from matplotlib.matlab import *
    >>> x=arange(10)
    >>> plot(x)
    [<matplotlib.lines.Line2D instance at 0x40d5e94c>]

With the following in my .matplotlibrc file

backend      : TkAgg      # the default backend
numerix      : Numeric    # Numeric or numarray
interactive  : True       
toolbar      : toolbar2   # None | classic | toolbar2

Let me know what you find.

JDH


    >>>> from matplotlib.matlab import * x=arange(10) plot(x)
    Shin> Traceback (most recent call last): File "<stdin>", line 1,
    Shin> in ?  File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/matlab.py",
    Shin> line 1176, in plot lines = gca().plot(*args, **kwargs) File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/matlab.py",
    Shin> line 762, in gca return
    Shin> get_current_fig_manager().get_current_axis() File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/matlab.py",
    Shin> line 251, in get_current_fig_manager gcf() # creates an
    Shin> active figure as a side effect File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/matlab.py",
    Shin> line 771, in gcf return figure() File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/matlab.py",
    Shin> line 691, in figure figManager = new_figure_manager(num,
    Shin> figsize, dpi, facecolor, edgecolor, frameon) File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/backends/backend_gtkagg.py",
    Shin> line 25, in new_figure_manager thisFig = Figure(*args,
    Shin> **kwargs) File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/figure.py",
    Shin> line 52, in __init__ facecolor=facecolor,
    Shin> edgecolor=edgecolor, File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/patches.py",
    Shin> line 130, in __init__ Patch.__init__(self, **kwargs) File
    Shin> "/usr/lib/python2.3/site-packages/matplotlib/patches.py",
    Shin> line 48, in __init__ self.__dict__['set_%s'%abbrev] =
    Shin> getattr(self, 'set_%s'%func) AttributeError: Rectangle
    Shin> instance has no attribute 'set_antialiased'

    Shin> -- Daehyok Shin



    Shin> -------------------------------------------------------
    Shin> SF.Net email is sponsored by Shop4tech.com-Lowest price on
    Shin> Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic
    Shin> DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free
    Shin> Shipping and Free Gift.
    Shin> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
    Shin> _______________________________________________
    Shin> Matplotlib-users mailing list
    Shin> Mat...@li...
    Shin> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

>>>>> "Gary" == Gary Strangman <st...@nm...> writes:


    Gary> I recently found matplotlib and think it's _exactly_ what
    Gary> the python environment needs from the scientific perspective
    Gary> ... interactive plotting as good as (or better than)
    Gary> Matlab's, that also makes it easy for Matlab users to be
    Gary> converted. ;-) I'm very impressed in the
    Gary> effort-to-date. Unfortunately, other software I use forces
    Gary> me to stay with python2.2, and I'm having tremendous trouble
    Gary> building matplotlib for win32. Might someone have a pointer
    Gary> to a self-installing executable for matplotlib compiled
    Gary> against python2.2 that is a more recent version than
    Gary> v0.54.1??

    Gary> Thanks! And cheers to all the developers of this package.

Hi Gary - thanks for the kind words (and thanks for the stats module
as well, which I've been using intermittently for years).

There is a bug in the _tkagg extension in the python2.2 build which
has never been tracked down and fixed, which is why we stopped
releasing it.  You get a missing DLL error when you try and load it.
I opened _tkagg.pyd in dependency walker, and the DLL is one of the
Visual Studio .NET dlls - though sometimes dependency walker fives
false alarms.

As I write this, it occurs to me the problem that arose in 2.2 may
have been coincident in my changing build environments (I don't know
if Todd experienced a similar problem with his numarray builds with
tkagg and python2.2, but I think he may have ...).

The other backends still work fine for python2.2 (GTKAgg, WXAgg,
etc...).  I don't know if you can use these, though, since you
specifically mentioned interactivity in your post.  I'd be happy to
send this build to you if you like (I built it for 0.61.0 yesterday
after your email).

The other options are

 - I can try and build on my old computer where maybe the problem
   doesn't exist and hence tkagg would work

 - I can try and fix the problem!  Clearly the best solution, but I
   don't have any great leads right now.

Are you primarily a numarray or Numeric user?

Cheers,
JDH

I'm a newbie and am trying to create a financial chart that converts or =
plots a tick data to any time frame (ex. daily, intraday and etc...). =20

I'm also using data that is written in a text file.  I only see an =
example that uses Yahoo data.   =20

Could anybody help me on how I can do this?

Thank you.

Ryugan Mizuta

My first trial produced the following error message.
What problem do you think is in my installation?
I am using GtkAgg backend for matplotlib 0.6.1 version in Mandrake 10
and python 2.3.3.
Thanks.

>>> from matplotlib.matlab import *
>>> x=arange(10)
>>> plot(x)
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.3/site-packages/matplotlib/matlab.py", line
1176, in plot
    lines =  gca().plot(*args, **kwargs)
  File "/usr/lib/python2.3/site-packages/matplotlib/matlab.py", line
762, in gca
    return get_current_fig_manager().get_current_axis()
  File "/usr/lib/python2.3/site-packages/matplotlib/matlab.py", line
251, in get_current_fig_manager
    gcf()  # creates an active figure as a side effect
  File "/usr/lib/python2.3/site-packages/matplotlib/matlab.py", line
771, in gcf
    return figure()
  File "/usr/lib/python2.3/site-packages/matplotlib/matlab.py", line
691, in figure
    figManager = new_figure_manager(num, figsize, dpi, facecolor,
edgecolor, frameon)
  File
"/usr/lib/python2.3/site-packages/matplotlib/backends/backend_gtkagg.py", line 25, in new_figure_manager
    thisFig = Figure(*args, **kwargs)
  File "/usr/lib/python2.3/site-packages/matplotlib/figure.py", line 52,
in __init__
    facecolor=facecolor, edgecolor=edgecolor,
  File "/usr/lib/python2.3/site-packages/matplotlib/patches.py", line
130, in __init__
    Patch.__init__(self, **kwargs)
  File "/usr/lib/python2.3/site-packages/matplotlib/patches.py", line
48, in __init__
    self.__dict__['set_%s'%abbrev] = getattr(self, 'set_%s'%func)
AttributeError: Rectangle instance has no attribute 'set_antialiased'

-- 
Daehyok Shin 

Hi,

I recently found matplotlib and think it's _exactly_ what the python 
environment needs from the scientific perspective ... interactive plotting 
as good as (or better than) Matlab's, that also makes it easy for Matlab 
users to be converted. ;-) I'm very impressed in the effort-to-date. 
Unfortunately, other software I use forces me to stay with python2.2, and 
I'm having tremendous trouble building matplotlib for win32. Might someone 
have a pointer to a self-installing executable for matplotlib compiled 
against python2.2 that is a more recent version than v0.54.1??

Thanks! And cheers to all the developers of this package.

-best
Gary

> On Mon, 2004-08-09 at 15:19, John Hunter wrote:
>> Probably what Philipp is looking for is for fill_over to do some
>> linear interpolation between his data points, which I think gives the
>> least surprising results.  The attached code probably comes closer to
>> what he's looking for.
>
> John, you're quite right in your deduction.  For some reason I wasn't
> seeing exactly the behavior Philipp reported, although it was enough
> different from your result that I agree your code is closer to what is
> required.  His example code and yours give somewhat different results
> when used with the fill_over function on the matplotlib Web site.
>
> Boy, Python is fun...and I'm learning to like matplotlib a lot too.
>
> Steve
>
>
>

Good Morning and thank you for your help. With the new function code, the
filling works really great.

Thank you !


Philipp Weißmann

On Mon, 2004-08-09 at 15:19, John Hunter wrote:
> Probably what Philipp is looking for is for fill_over to do some
> linear interpolation between his data points, which I think gives the
> least surprising results.  The attached code probably comes closer to
> what he's looking for.

John, you're quite right in your deduction.  For some reason I wasn't
seeing exactly the behavior Philipp reported, although it was enough
different from your result that I agree your code is closer to what is
required.  His example code and yours give somewhat different results
when used with the fill_over function on the matplotlib Web site.

Boy, Python is fun...and I'm learning to like matplotlib a lot too.

Steve

On Tue, 2004-08-10 at 00:55, John Hunter wrote:
> Also, Steve, we might be better off here catching *all* exceptions
> rather than just the gobject error.  Darren, would you test to see if
> this works
> 
> 
> # set icon used when windows are minimized
> if gtk.pygtk_version >= (2,2,0):
>     basedir = matplotlib.rcParams['datapath']
>     fname = os.path.join(basedir, 'matplotlib.svg')
>     try:   gtk.window_set_default_icon_from_file (fname)
>     except: print >>sys.stderr, 'Could not load matplotlib icon'

I've changed this code section of backend_gtk.py in cvs so it catches
all exceptions, prints a warning and continues running, rather than
aborting on unknown exceptions.

Steve

I was thinking about the way the labels are formatted. Some of the 
numbers I work with are large(10^10) and small (10^-10), and the 
formatting wasnt quite right. I am running the following as a test:

mport matplotlib
from matplotlib.matlab import *
from numarray import array

a=array(range(10))*1e6+1e7
b = array(range(10))*1e-5+1e-4
plot(a,b)

in ticker.py, in ScalarFormatter, what is the purpose of this routine?

        # if the value is just a fraction off an int, use the int
        if abs(x-long(x))<0.0001*d:
            if x<=10000: return '%d' % long(x + 0.5)
            else: return '%1.0e'%long(x)

If commented out, the labels are formatted appropriately as 
exponentials, otherwise, the level of precision can often not be useful. 
Also, in the exponential formatting block, might this
if d < 1e-3: fmt = '%1.3f'
read this?:
if d < 1e-2: fmt = '%1.3e'

One final suggestion, for formatting the exponential component:

m = self._zerorgx.match(s)
        if m:
            s = m.group(1)
            if m.group(2) is not None:
##                 s += m.group(2)
                s += m.group(2)[:2]+str(int(m.group(2)[2:])) ## my hack 
to make 3e003 look like 3e3. (Whats the "right way"?)
        s = s.replace('+', '')
        return s

Darren

>>>>> "Stephen" == Stephen Walton <ste...@cs...> writes:

    Stephen> It looks to me, when running your code, that fill_over is
    Stephen> doing the right thing: filling everything between 0.5 and
    Stephen> your plotted line with a color.  It is just that with
    Stephen> your coarse spacing, you don't have points at every
    Stephen> multiple of pi/2.  However, this is with the current CVS
    Stephen> version, so you may have a problem with 0.60.2.

Probably what Philipp is looking for is for fill_over to do some
linear interpolation between his data points, which I think gives the
least surprising results.  The attached code probably comes closer to
what he's looking for.  It's probably a useful function to include in
the library - see if it meets your needs

from matplotlib.matlab import *

def fill_over(ax, x, y, val, color, over=True):
    """
    Plot filled x,y for all y over val

    If over = False, fill under
    """
    x = asarray(x).astype(nx.Float32)
    y = asarray(y).astype(nx.Float32)
    ybase = asarray(y)-val
    crossings = nonzero(less(ybase[:-1] * ybase[1:],0))
    
    on = not over
    indLast = 0
    for ind in crossings:        
        if not on:
	   on = not on
	   indLast = ind
	   continue
	thisX = array(x[indLast:ind+2]) 
	thisY = array(y[indLast:ind+2]) 
	#find the x point between x[0] and x[1] on the line
	#connecting them such that f(x) = 0.5
	#if len(thisX)<3: continue
	m = (thisY[1]-thisY[0])/(thisX[1]-thisX[0])
	x0 = (val-thisY[0])/m+thisX[0]

	thisX[0] = x0
	thisY[0] = val

	# now get the last point on the interpolated line
	m = (thisY[-1]-thisY[-2])/(thisX[-1]-thisX[-2])
	xend = (val-thisY[-2])/m+thisX[-2]

	thisX[-1] = xend
	thisY[-1] = val
	on = not on
	ax.fill(thisX, thisY, color)
	indLast = ind


x=arange(0.0, 20.0, 1.0)
y = sin(x)

plot(x,y, 'ro-')
fill_over(gca(), x, y, 0.5, '#0000FF', over=True)

show()

On Mon, 2004-08-09 at 13:44, Philipp Weissmann wrote:

> when using fill_over, it does not draw exactly at one line but with a=20
> slightly aberration. This especially is horrible when using a low=20
> resolution:

It looks to me, when running your code, that fill_over is doing the
right thing:  filling everything between 0.5 and your plotted line with
a color.  It is just that with your coarse spacing, you don't have
points at every multiple of pi/2.  However, this is with the current CVS
version, so you may have a problem with 0.60.2.

Is fill_over supported in any way?  I had a problem finding it, and it
looks like it is in the category of unsupported contribted code.

By the way, Herr Weissman, setting up your sample data can be done
simply by typing

x=3Darange(0,20)
y=3Dsin(x)

without 'x=3D[]', 'y=3D[]', or the for loop.

--=20
Stephen Walton <ste...@cs...>
Dept. of Physics & Astronomy, Cal State Northridge

>    Darren> After upgrading to Matplotlib 0.61, I am getting the
>    Darren> following error: Unable to load image-loading module:
>    Darren> C:\Program Files\Common
>    Darren> Files\GTK\2.0/lib/gtk-2.0/2.2.0/loaders/svg_loader.dll
>
>    Darren> The path is correct, the file exists, I wonder if the
>    Darren> mixed path seperators is causing trouble? I cant find the
>    Darren> location of this exception in matplotlib to look into it,
>    Darren> where should I look?
>
> I'm note getting this error. My guess is that it is coming from the
> final lines of backend_gtk.py
>
> # set icon used when windows are minimized
> if gtk.pygtk_version >= (2,2,0):
>    basedir = matplotlib.rcParams['datapath']
>    fname = os.path.join(basedir, 'matplotlib.svg')
>    try:   gtk.window_set_default_icon_from_file (fname)
>    except gobject.GError, exc: print >>sys.stderr, exc
>
> My win32 pygtk is older than 2.2.0 which may be why I am not seeing it.
> Would you mind seeing if this is indeed the problem (for starters,
> just replace the conditional with 'if 0:'.  If you get any more
> insight into the problem, be sure and let me know!
>
> Also, Steve, we might be better off here catching *all* exceptions
> rather than just the gobject error.  Darren, would you test to see if
> this works
>
>
> # set icon used when windows are minimized
> if gtk.pygtk_version >= (2,2,0):
>    basedir = matplotlib.rcParams['datapath']
>    fname = os.path.join(basedir, 'matplotlib.svg')
>    try:   gtk.window_set_default_icon_from_file (fname)
>    except: print >>sys.stderr, 'Could not load matplotlib icon'
>  
>
I tried this, and then started getting popups about dll's not being 
found. svg_loader.dll was not the problem.

The following were missing from Common Files\GTK\2.0\bin:
librsvg-2-2.dll
libart_lgpl_2-2.dll
libgsf-1-1.dll
libxml2.dll
zlib.dll

I had copies of all of these in my Gimp/bin directory, with the 
exception of zlib. At some point, months ago, I had downloaded zipfiles 
of all of these dll's, including zlib121 (not sure what I downloaded 
them for, probably the Gimp). Unzipped, zlib121 is called zlib1.dll, I 
renamed it zlib.dll and saved it with the other missing dll's in the 
GTK\2.0\bin. After resolving a dll clash (existing but incompatible 
zlib.dll in windows/system32), I think it is working.

By the way, the new toolbar is NICE. I like that Matplotlib is branding 
its windows, too, but what happened to the cardiogram? Matplotlib is too 
cool for a sin function, maybe the Strange Attractor is more 
appropriate? (Seems like something a Mac programmer would try.)

Darren

John,
Clean install worked.  Must have had some version
leftovers around.

Thanks.
Barry

--- John Hunter wrote:
> >>>>> "Barry" == Barry Drake
<>
> writes:
> 
>     Barry> This means that it gets past the
> try-except in
>     Barry> backend_wx.py, but can't find
> wxPySimpleApp.
> 
> Are you using the standard python shell or an IDE
> like pycrust?  If
> the latter, it may be overriding the sys,exit
which
> is why you aren't
> seeing it.  From your previous post, it looks
like
> your wx
> installation is in bad shape.  Until you can do
> 'from wxPython.wx
> import *' from the standard python shell, I
wouldn't
> bother with
> trying to tweak matplotlib.
> 
> I didn't see any error message like the one you
were
> getting in the
> wxpython archives - you might try the wx mailing
> list.
> 
> JDH
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you
> noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the
> past few weeks? Now,
> one more big change to announce. We are now OSTG-
> Open Source Technology
> Group. Come see the changes on the new OSTG site.
> www.ostg.com
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
>
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hallo matplitlib userse,

when using fill_over, it does not draw exactly at one line but with a 
slightly aberration. This especially is horrible when using a low 
resolution:
The following program draws a nice sinus-curve and fills all values 
above 0.5. But when reducing the resolution (i.e. set the variable res 
to "1") fill_over generates weird fillings.

from matplotlib.matlab import *
from matplotlib.helpers import *
res=0.1
# < 0.1 -> nice resolution
# > 1 -> weird fillings
x=[]
y=[]
x=arange(0,20,res)
for i in x:
	y.append(sin(i))
r=axes()
r.plot(x,y);
fill_over(r,x,y, 0.5, '#0000FF',over=True)
show()
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBF+JHQz7EsHuNmkoRAg86AJkBLwXFD+ShYKh/k9p7ZnRLbJQarACghr7U
3fjj7ejBOl/XxB854CgfYD0=
=zPc3
-----END PGP SIGNATURE-----

What's new in matplotlib-0.61.0 - 

  Note win32 pygtk users - if you encounter problems or errors related
  to svg loading, see note at end of this email.

You can read these announce notes in html with hyperlinks at
http://matplotlib.sf.net/whats_new.html.

 * A new, enhanced, navigation toolbar.  Set 'toolbar : toolbar2' in
   matplotlibrc to try it out.  Tutorial on the new toolbar is at
   http://matplotlib.sf.net/tutorial.html#toolbar2.  Note that this
   toolbar behaves very differently than the classic toolbar.  To use
   it, you must click on the pan/zoom or zoom to rect and then
   interact with the axes by dragging your mouse over it.  The
   'forward', 'back' and 'home' buttons are used to navigate between
   previously defined view limits.  At some point we'll add multiple
   simultaneous axes support for the new toolbar but we're still
   mulling over the interface - if you need it you can still uses
   toolbar : classic.

 * Mathtext for PS!!!  Also, PS now embeds TrueType fonts so the same
   fonts you use in the *Agg GUIs should be displayed in PS
   output. Thanks Paul Barrett!

 * The imread function is used to load PNGs into arrays.  I'd like to
   add more image loaders and savers down the road -
   http://matplotlib.sourceforge.net/matplotlib.matlab.html#-imread

 * New event handling.  The functions mpl_connect and mpl_disconnect
   are used for backend independent event handling.  The callback
   signature is func(event).  See
   http://matplotlib.sf.net/tutorial.html#events and
   http://matplotlib.sf.net/examples/coords_demo.py.  The new events
   carry lots of useful information in them, like the coords in
   display and data units, the axes instance they were over, keys
   pressed during the event and more.

 * Many fixes to the SVG backend, including page layout, font support
   and image support.  SVG is now considered alpha.  You can save
   ps/eps/svg figures from GUI backends by providing the right
   extensions.  SVG is currently the fastest backend in my tests.

 * More memory leaks fixed - see
   http://matplotlib.sourceforge.net/faq.html#LEAKS for details.  My
   estimate is that complex figures (multiple subplots, images, etc..)
   now leak no more than 10-50 bytes per figure.  Down from several
   hundred bytes per figure in 0.60.

 * Vertical mathtext in backend_agg (ylabels now work properly!).
   mathtext with arbitrary rotations in PS.  Thanks Jim Benson and
   Paul Barrett!

 * Added some abbrev functions in matplotlib.lines, mainly for
   interactive users trying to save key strokes.  markerfacecolor is a
   lot of keys!  For lines, these abbrevs were added

        aa  : antialiased
        c   : color
        ls  : linestyle
        lw  : linewidth
        mec : markeredgecolor
        mew : markeredgewidth
        mfc : markerfacecolor
        ms  : markersize

   Thus you can type --not necessarily recommended for readability in
   scripts or apps but great for throwaway use in interactive shells
    
    # no antialiasing, thick green markeredge lines
    >>> plot(range(10), 'ro', aa=False, mew=2, mec='g')

   Analogs in matplotlib.patches

        aa  : antialiased
        lw  : linewidth
        ec  : edgecolor
        fc  : facecolor

 * You can put a .matplotlibrc file in a dir to override the one in
   your HOME dir.  If you have a project, say a book, and you want to
   make a bunch of images with the same look and feel for the book,
   you can place a custom rc file in the code dir for that book and
   this won't affect the configs you use for normal, interactive use.

 * Updated installing instructions at
   http://matplotlib.sf.net/installing.html (see also INSTALL in src
   distro).  Fixed a tk/osx install problem in setupext.py

 * New demo for wx/wxagg showing how to to make a flicker free cursor
   that follows the mouse and reports the coords in a status bar - see
   http://matplotlib.sf.net/examples/wxcursor_demo.py

 * Numerous bug fixes and minor enhancements detailed at
   http://matplotlib.sf.net/CHANGELOG

Downloads at http://sourceforge.net/projects/matplotlib


pygtk / win32 bug

  Alas, an enterprising matplotlib user found a bug in matplotlib-0.61
  on win32 with recent versions of pygtk even before the announcement.
  Sigh.  Is it just me or is testing multiple GUIs with multiple,
  incompatible versions on multiple platforms a pain?  

  Apparently this bug is only exposed on recent versions of pygtk for
  win32.  If you encounter problems, try removing or commenting out
  the last lines of site-packages\matplotlib\backends\backend_gtk.py
  which set the matplotlib minimization icon.  Eg, triple quote

"""
# set icon used when windows are minimized
if gtk.pygtk_version >= (2,2,0):
    basedir = matplotlib.rcParams['datapath']
    fname = os.path.join(basedir, 'matplotlib.svg')
    try:   gtk.window_set_default_icon_from_file (fname)
    except gobject.GError, exc: print >>sys.stderr, exc
"""

John,
I'm using a windows XP shell; so no extra stuff
running.

I did run all of the wxPython 2.5 demos before trying
my old matplotlib code.  The wxPython demos ran fine.

My "old" matplotlib code ran under matplotlib 0.54.2
with wxPython 2.4.1.2; I tested all of the backends
with success.

After upgrading to wxPython 2.5 all of my matplotlib
code is broken.  I even upgraded to the latest
matplotlib, 0.61.  Still doesn't work.

I'll try a clean reinstall next.  If that doesn't work
I'll go to the wx lists.

Thanks.
Barry

--- John Hunter wrote:
> >>>>> "Barry" == Barry Drake
<>
> writes:
> 
>     Barry> This means that it gets past the
> try-except in
>     Barry> backend_wx.py, but can't find
> wxPySimpleApp.
> 
> Are you using the standard python shell or an IDE
> like pycrust?  If
> the latter, it may be overriding the sys,exit
which
> is why you aren't
> seeing it.  From your previous post, it looks
like
> your wx
> installation is in bad shape.  Until you can do
> 'from wxPython.wx
> import *' from the standard python shell, I
wouldn't
> bother with
> trying to tweak matplotlib.
> 
> I didn't see any error message like the one you
were
> getting in the
> wxpython archives - you might try the wx mailing
> list.
> 
> JDH
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you
> noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the
> past few weeks? Now,
> one more big change to announce. We are now OSTG-
> Open Source Technology
> Group. Come see the changes on the new OSTG site.
> www.ostg.com
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
>
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

>>>>> "Jin-chung" == Jin-chung Hsu <hs...@st...> writes:

    Jin-chung> One would expect the following will fill up the plot
    Jin-chung> window:
    >>>> n=zeros(20000) n[::2]=1 plot(n)

    Jin-chung> The plot "stops" a little more than half way, as if it
    Jin-chung> "runs out of ink".

    Jin-chung> It happens on Linux as well as Solaris, using either
    Jin-chung> numarray and Numeric, and both TkAgg and GTKAgg, but
    Jin-chung> not GTK.  Is this due to some AGG limitation?


A bit more information on this problem - I just got this post from
Maxim on the Agg mailing list

    Hi John,

    You have this wierdness because your path is too long, it exceeds
    the maximal limit of memory allowed for the scanline
    rasterizer. It's 4196*1024 cells (pixels), or 67MB. I added this
    limit in order not to crash the whole system in case if you or I
    have an infinite loop of rasterizer::line_to. I'm not sure if it's
    the best solution, but I don't see anything better. What is the
    necessity to draw such long uninterrupted paths?

    McSeem

This explains several of the "strange observations".  The problem
occured when the axes limits were [-1,1] and not [-2,2] because in the
latter case the pixel coverage was smaller.  It occured for plotting
solid lines but not for circles for the same reason.

Probably the best solution is to break long line paths into multiple
paths in the agg backend.  It should be a pretty rare event - there
aren't too many plots that try and cover that many pixels with lines,
but it does happen and should be accounted for...

JDH

>>>>> "Jin-chung" == Jin-chung Hsu <hs...@st...> writes:

    Jin-chung> Hi: I have encountered several problems with plot_date.
    Jin-chung> I am using 0.60.1 (maybe fixed in 0.60.2?) on Solaris.

    Jin-chung> (1) If I put a smaller number as one of the dates (as
    Jin-chung> seconds), it raises the "before the epoch" error.  But
    Jin-chung> I think plot_date should accomodate dates earlier than
    Jin-chung> 1970.


Yes, this is on the goals page - when I implemented the dates module,
I wanted to be able to support python2.2, and thus fell back on the
time module which is based on the epoch.  It's a limitation that needs
to be addressed.  On possibility is to require python2.3 for datetime
support - probably better is to use datetime and an earlier epoch
where available.

    Jin-chung> (2) After the error in (1) happens, even if I put
    Jin-chung> "legal" dates and run plot_date again, it still issues
    Jin-chung> the same error.  It seems there is some kind of switch
    Jin-chung> needs to be reset.

Does cla() help - normally all plot data is kept around until the axes
are cleared.  This happens by default is axes.hold is False in rc or
if you manually set

  >>> hold(False)

If you still have the problem after the axes are cleared, let me know
because then it's a bug.

    Jin-chung> (3) if, e.g. t=[1.e8, 1.1e8], the x-axis tick labels
    Jin-chung> are crowded.

This appears to be fixed in 0.61 with Peter Groszkowski
MultiWeekLocator submission.

Thanks,
JDH

Hi:

I have encountered several problems with plot_date.  I am using 0.60.1 (maybe 
fixed in 0.60.2?) on Solaris.

(1) If I put a smaller number as one of the dates (as seconds), it raises the 
"before the epoch" error.  But I think plot_date should accomodate dates earlier 
than 1970. 

>>> t=[1.e7, 1.e8]
>>> plot_date(t,y,None)
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/ra/pysoft/2.3.3/matplotlib/matlab.py", line 1207, in plot_date
    try: lines =  gca().plot_date(*args, **kwargs)
  File "/usr/ra/pysoft/2.3.3/matplotlib/axes.py", line 1496, in plot_date
    ret = self.plot(e, y, fmt, **kwargs)
  File "/usr/ra/pysoft/2.3.3/matplotlib/axes.py", line 1472, in plot
    self.autoscale_view()
  File "/usr/ra/pysoft/2.3.3/matplotlib/axes.py", line 445, in autoscale_view
    tup = locator.autoscale()
  File "/usr/ra/pysoft/2.3.3/matplotlib/ticker.py", line 728, in autoscale
    dmin = self.epochConverter.floor_month(dmin)
  File "/usr/ra/pysoft/2.3.3/matplotlib/dates.py", line 354, in floor_month
    if y<1970: raise RuntimeError('You are before the epoch!')
RuntimeError: You are before the epoch!


(2) After the error in (1) happens, even if I put "legal" dates and run 
plot_date again, it still issues the same error.  It seems there is some kind of 
switch needs to be reset.

(3) if, e.g. t=[1.e8, 1.1e8], the x-axis tick labels are crowded.


JC Hsu

>>>>> "Barry" == Barry Drake <bl...@ad...> writes:

    Barry> This means that it gets past the try-except in
    Barry> backend_wx.py, but can't find wxPySimpleApp.

Are you using the standard python shell or an IDE like pycrust?  If
the latter, it may be overriding the sys,exit which is why you aren't
seeing it.  From your previous post, it looks like your wx
installation is in bad shape.  Until you can do 'from wxPython.wx
import *' from the standard python shell, I wouldn't bother with
trying to tweak matplotlib.

I didn't see any error message like the one you were getting in the
wxpython archives - you might try the wx mailing list.

JDH

Update to my previous post:

When I use the command line to use WXAgg, I receive
the following traceback:
>>> import matplotlib
>>> matplotlib.use("WXAgg")
>>> from matplotlib.matlab import *
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File
"C:\Python23\Lib\site-packages\matplotlib\matlab.py",
line 144, in ?
    from backends import new_figure_manager,
error_msg, \
  File
"C:\Python23\Lib\site-packages\matplotlib\backends\__init__.py",
line 39, in ?
    from backend_wxagg import \
  File
"C:\Python23\Lib\site-packages\matplotlib\backends\backend_wxagg.py",
line 20, in ?
    from backend_wx import FigureManager
  File
"C:\Python23\Lib\site-packages\matplotlib\backends\backend_wx.py",
line 116, in ?
    wxapp = wxPySimpleApp()
NameError: name 'wxPySimpleApp' is not defined

This means that it gets past the try-except in
backend_wx.py, but can't find wxPySimpleApp.

In the previous post, when runing the code from a
file, the exception was caught and 
a sysexit() occurred.

I don't understand why in one case the exception is
caught and not in the other.
In either case, I'm still unable to use the wx
backend.

Thanks.
Barry Drake

--- Barry Drake wrote:
&gt; Having a problem with the WX backend; details
&gt; follow.
&gt; 
&gt; I have wxPython 2.5 and
&gt; matplotlib-0.60.2.win32-py2.3
&gt; installed.
&gt; 
&gt; My code snippet:
&gt; import matplotlib
&gt; matplotlib.use("WXAgg")
&gt; from matplotlib.matlab import *
&gt; 
&gt; Error msg:
&gt; Matplotlib backend_wx requires wxPython be
installed
&gt; 
&gt; Code snippet from:
&gt;
C:\Python23\Lib\site-packages\matplotlib\backends\backend_wx.py
&gt; try:
&gt;     from wxPython.wx import *
&gt; except:
&gt;     print &gt;&gt;sys.stderr, "Matplotlib
backend_wx
&gt; requires wxPython be installed"
&gt;     sys.exit()    
&gt; 
&gt; I receive the following traceback when I try to
&gt; invoke
&gt; this from the command line:
&gt; 
&gt; Enthought Edition build 1057
&gt; Python 2.3.3 (#51, Feb 16 2004, 04:07:52) [MSC
&gt; v.1200
&gt; 32 bit (Intel)] on win32
&gt; Type "help", "copyright", "credits" or "license"
for
&gt; more information.
&gt; &gt;&gt;&gt; from wxPython.wx import *
&gt; Traceback (most recent call last):
&gt;   File "&lt;stdin&gt;", line 1, in ?
&gt;   File
&gt;
"C:\Python23\lib\site-packages\wxPython\__init__.py",
&gt; line 10, in ?
&gt;     import _wx
&gt;   File
&gt; "C:\Python23\Lib\site-packages\wxPython\_wx.py",
&gt; line
&gt; 3, in ?
&gt;     from core import *
&gt;   File
&gt; "C:\Python23\Lib\site-packages\wxPython\core.py",
&gt; line
&gt; 15, in ?
&gt;     import wx.core
&gt;   File
&gt; "C:\Python23\lib\site-packages\wxPython\wx.py",
&gt; line 4, in ?
&gt;     from misc import *
&gt;   File
&gt; "C:\Python23\lib\site-packages\wxPython\misc.py",
&gt; line
&gt; 15, in ?
&gt;     import wx.misc
&gt;   File
&gt; "C:\Python23\lib\site-packages\wxPython\wx.py",
&gt; line 6, in ?
&gt;     from misc2 import *
&gt;   File
&gt;
"C:\Python23\lib\site-packages\wxPython\misc2.py",
&gt; line 4, in ?
&gt;     from windows import *
&gt;   File
&gt;
"C:\Python23\lib\site-packages\wxPython\windows.py",
&gt; line 15, in ?
&gt;     import wx.windows
&gt;   File
&gt; "C:\Python23\lib\site-packages\wxPython\wx.py",
&gt; line 10, in ?
&gt;     from gdi import *
&gt;   File
&gt; "C:\Python23\lib\site-packages\wxPython\gdi.py",
&gt; line
&gt; 15, in ?
&gt;     import wx.gdi
&gt;   File
&gt; "C:\Python23\lib\site-packages\wxPython\wx.py",
&gt; line 12, in ?
&gt;     from fonts import *
&gt;   File
&gt;
"C:\Python23\lib\site-packages\wxPython\fonts.py",
&gt; line 120, in ?
&gt;     class wxFontPtr(wxObjectPtr):
&gt; NameError: name 'wxObjectPtr' is not defined
&gt; 
&gt; code snippet from:
&gt; C:\Python23\Lib\site-packages\wxPython\fonts.py
&gt; class wxFontPtr(wxObjectPtr):
&gt; 
&gt; This doesn't seem to be a problem specific to
&gt; matplotlib.  But, I'm wondering if anyone has
&gt; already solved this or I'm just missing
something.
&gt; 
&gt; Thanks.
&gt; Barry Drake
&gt; 
&gt; 
&gt; 
&gt;
-------------------------------------------------------
&gt; This SF.Net email is sponsored by OSTG. Have you
&gt; noticed the changes on
&gt; Linux.com, ITManagersJournal and NewsForge in the
&gt; past few weeks? Now,
&gt; one more big change to announce. We are now OSTG-
&gt; Open Source Technology
&gt; Group. Come see the changes on the new OSTG site.
&gt; www.ostg.com
&gt; _______________________________________________
&gt; Matplotlib-users mailing list
&gt; Mat...@li...
&gt;
https://lists.sourceforge.net/lists/listinfo/matplotlib-users