matplotlib-users Mailing List for matplotlib

At 2:38 PM -0800 2006-11-08, Christopher Barker wrote:
>Russell E. Owen wrote:
>>I reinstalled wxPython 2.7 from the package at pythonmac.org (to be 
>>paranoid). I'm using the Python 2.5 version.
>
>check
>
>>I got wx-config on my path and confirmed it's the right one (see 
>>below for details).
>
>check.
>
>>Now when I try to build matplotlib it fails. Ouch.
>>
>>It starts out with the same warning as last time:
>>setup.py:267: DeprecationWarning: The wxPython compatibility 
>>package is no longer automatically generated or activly maintained. 
>>Please switch to the wx package as soon as possible.
>>   import wxPython
>
>This one is easy!
>
>In setup.py, replace:
>
>import wxPython
>
>with
>
>import wx
>
>A few versions ago, the "import wxPython" form was deprecated -- it 
>is now gone in 2.7. IN this case, all it's doing it checking if 
>wxPython is installed, so th import wx should be the only change 
>needed.

Got it. Thanks! Should I submit a patch?

Unfortunately "python setup.py build" still fails when compiling 
_wxagg (in the same way as last time). I've appended the log so the 
whole list can enjoy it.

I should probably be using wxPython 2.6.x. I originally thought 
wxPython 2.7 was the current release but as you pointed out, that was 
a misconception. Unfortunately, it's the only binary package 
available for Python 2.5 at pythonmac.org.

-- Russell

$ python setup.py build
GTK requires pygtk
GTKAgg requires pygtk
running build
running build_py
running build_ext
building 'matplotlib.backends._wxagg' extension
C compiler: gcc -arch ppc -arch i386 -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double 
-no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3

creating build/temp.macosx-10.3-fat-2.5
creating build/temp.macosx-10.3-fat-2.5/src
creating build/temp.macosx-10.3-fat-2.5/CXX
compile options: '-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXDEBUG__ 
-D__WXMAC__ -I/usr/local/include -I/usr/include -I. -Isrc -Iswig 
-Iagg23/include -I. -I/usr/local/include -I/usr/include -I. 
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2 
-Isrc/freetype2 -Iswig/freetype2 -Iagg23/include/freetype2 
-I./freetype2 -I/usr/local/include/freetype2 -I/usr/include/freetype2 
-I./freetype2 -I/usr/local/include -I/usr/include -I. 
-I/usr/local/lib/wxPython-unicode-2.7.1.3/lib/wx/include/mac-unicode-debug-2.7 
-I/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7 
-I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 
-c'
gcc: CXX/cxxextensions.c
gcc: CXX/cxx_extensions.cxx
gcc: CXX/IndirectPythonInterface.cxx
gcc: src/_wxagg.cpp
src/_wxagg.cpp: In function 'wxBitmap* 
convert_agg2bitmap(RendererAgg*, Bbox*)':
src/_wxagg.cpp:238: error: conversion from 'wxImage*' to 'const 
wxString' is ambiguous
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:686: 
note: candidates are: wxString::wxString(wxChar, size_t) <near match>
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:676: 
note:                 wxString::wxString(int) <near match>
src/_wxagg.cpp: In function 'wxBitmap* 
convert_agg2bitmap(RendererAgg*, Bbox*)':
src/_wxagg.cpp:238: error: conversion from 'wxImage*' to 'const 
wxString' is ambiguous
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:686: 
note: candidates are: wxString::wxString(wxChar, size_t) <near match>
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:676: 
note:                 wxString::wxString(int) <near match>
lipo: can't figure out the architecture type of: /var/tmp//cc135E90.out
src/_wxagg.cpp: In function 'wxBitmap* 
convert_agg2bitmap(RendererAgg*, Bbox*)':
src/_wxagg.cpp:238: error: conversion from 'wxImage*' to 'const 
wxString' is ambiguous
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:686: 
note: candidates are: wxString::wxString(wxChar, size_t) <near match>
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:676: 
note:                 wxString::wxString(int) <near match>
src/_wxagg.cpp: In function 'wxBitmap* 
convert_agg2bitmap(RendererAgg*, Bbox*)':
src/_wxagg.cpp:238: error: conversion from 'wxImage*' to 'const 
wxString' is ambiguous
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:686: 
note: candidates are: wxString::wxString(wxChar, size_t) <near match>
/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7/wx/string.h:676: 
note:                 wxString::wxString(int) <near match>
lipo: can't figure out the architecture type of: /var/tmp//cc135E90.out
error: Command "gcc -arch ppc -arch i386 -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double 
-no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 
-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXDEBUG__ -D__WXMAC__ 
-I/usr/local/include -I/usr/include -I. -Isrc -Iswig -Iagg23/include 
-I. -I/usr/local/include -I/usr/include -I. 
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2 
-Isrc/freetype2 -Iswig/freetype2 -Iagg23/include/freetype2 
-I./freetype2 -I/usr/local/include/freetype2 -I/usr/include/freetype2 
-I./freetype2 -I/usr/local/include -I/usr/include -I. 
-I/usr/local/lib/wxPython-unicode-2.7.1.3/lib/wx/include/mac-unicode-debug-2.7 
-I/usr/local/lib/wxPython-unicode-2.7.1.3/include/wx-2.7 
-I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 
-c src/_wxagg.cpp -o build/temp.macosx-10.3-fat-2.5/src/_wxagg.o" 
failed with exit status 1

Hi NG,

    I posted this question few months ago and I didn't receive any
answer, so I'll try to rephrase my problem.

I have a GUI written in wxPython, the main portion of it is a
matplotlib canvas. There is a tree control on the left with
checkboxes: if the user checks a checkbox, I add a line on the plot.
So far so good. The problem comes when the user *un-checks* the
checkbox. I would like to remove the line from the plot, but the only
way I found to do it is to do:

line.set_linestyle("None")

Which is not very nice (and not very correct), as it seems to me that
the line is still there (invisible, but still there). Am I right or
have I completely misunderstood the set_linestyle behavior? If this
method is not correct, is there any alternative that I could try to
erase completely the line from the plot (and from the legend,
obviously)?
The alternative of replotting everything just because a line should be
erased came into my mind but I discarded it because it is
fantastically time consuming with my graphs.

Thank you for every hint.

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.virgilio.it/infinity77/

Hello!

I'm dynamically dishing out plots via matplotlib through a web server,
so I really want to savefig to some type of memory object.

Using both os.pipe and cStringIO objects, I get this type of error:


In [9]:%history
1 : import matplotlib
2 : matplotlib.use('Agg')
3 : import pylab
4 : ax = pylab.gca()
5 : ax.specgram( range(100) )
6 : import cStringIO
7 : sbuf = cStringIO.StringIO()
8 : pylab.savefig( sbuf, format='png' )



In [8]:pylab.savefig( sbuf, format='png' )
---------------------------------------------------------------------------
exceptions.TypeError                                 Traceback (most
recent call last)

/home/gmabey/src/R9619_zippy/Projects/R9619_NChannelDetection/AcqLibWeb/<ipython console> 

/usr/local/stow/matplotlib-0.87.7/lib/python2.4/site-packages/matplotlib/pylab.py
in savefig(*args, **kwargs)
    811 def savefig(*args, **kwargs):
    812     fig = gcf()
--> 813     return fig.savefig(*args, **kwargs)
    814 if Figure.savefig.__doc__ is not None:
    815     savefig.__doc__ = _shift_string(Figure.savefig.__doc__)

/usr/local/stow/matplotlib-0.87.7/lib/python2.4/site-packages/matplotlib/figure.py
in savefig(self, *args, **kwargs)
    680                 kwargs[key] = rcParams['savefig.%s'%key]
    681 
--> 682         self.canvas.print_figure(*args, **kwargs)
    683 
    684     def colorbar(self, mappable, cax=None, **kw):

/usr/local/stow/matplotlib-0.87.7/lib/python2.4/site-packages/matplotlib/backends/backend_agg.py
in print_figure(self, filename, dpi, facecolor, edgecolor, orientation,
**kwargs)
    458         if not is_string_like(filename):
    459             # assume png and write to fileobject
--> 460             self.renderer._renderer.write_png(filename)
    461             #pass
    462         else:

TypeError: Could not convert object to file pointer
> /usr/local/stow/matplotlib-0.87.7/lib/python2.4/site-packages/matplotlib/backends/backend_agg.py(460)print_figure()
    459             # assume png and write to fileobject
--> 460             self.renderer._renderer.write_png(filename)
    461             #pass



I'm a bit confused as to where the exception is actually getting raised.
I suppose the renderer's write_png method must be in C?

I implemented a tempfile solution, but I'm surprised that the cStringIO
doesn't already work.  

<fellowsophical_question>

Should it?

</fellowsophical_question>

Thanks,
Glen

>>>>> "Yannick" == Yannick Copin <y....@ip...> writes:

    Yannick> Hi, I'd like to use axhspan, but specifying both y *and*
    Yannick> x extents in *data* units (by default, y is specified in
    Yannick> data units, and x in axes -- relative 0-1 -- units). How
    Yannick> should I proceed?

    Yannick> I naively tried to play with gca().transAxes and so on,
    Yannick> but I must admit I was utterly confused...

    Yannick> Or should I directly draw a rectangle? (but how to?)

Yes, you should draw a rectangle.  Eg, 

  from matplotlib.patches import Rectangle
  r = Rectangle((left, bottom), width, height, facecolor='red')
  ax.add_patch(r)

One thing to be aware of is that the axes datalimits are not updated
on a call to add_patch, so autoscaling may be off.  You can update the
datalim yourself by doing

  ax.update_datalim([(left, bottom), (right, top)])

and then

  ax.autoscale_view()

It might be worth adding some convenience functions to draw basic
primitives like this, ie one would rather do

  ax.rectangle((left, bottom), width, height, facecolor='red')

or

  ax.circle((x,y), radius=5, edgecolor='green')

and not have to worry about the rest

JDH
 

I am on windows with mpl 0.87.2.

Seweryn Kokot wrote:
> I can report the same problem with polish characters. Using WX and GTK it
> works but when using WXAgg or GTKAgg it doesn't.
> I wrote about this problem some time ago on this group but no
> response.
> So we are two. 
> I can add that the problem ocurrs in mpl 0.87.5 (debian sid) and not
> in mpl 0.87.2 (debian sarge).
>
> regards,
> SK
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>   

I can report the same problem with polish characters. Using WX and GTK it
works but when using WXAgg or GTKAgg it doesn't.
I wrote about this problem some time ago on this group but no
response.
So we are two. 
I can add that the problem ocurrs in mpl 0.87.5 (debian sid) and not
in mpl 0.87.2 (debian sarge).

regards,
SK

Hi everybody,

I try to make a plot using chineese strings (unicode).
The folowing code works :

# -*- coding: utf-8 -*-
import matplotlib
matplotlib.use('WX')
import pylab as p

p.plot((1,2,3))
p.xlabel( '=E6=98=AF=E6=9C=80=E5=A5=BD=E7=9A=84=E7=B7=A8=E7=A8=8B=E8=AA=9E=
=E8=A8=80')
p.text(0.5,1.5,u'=C3=A9=C3=A7=C3=A8')
p.show()

But the same code using WxAgg or TkAgg does not works (strings are not
displayed correctly). Is someone have an idea about this problem ?

Thanks.

Olivier

Hello,

I have a very weird problem with matplotlib and reals. Before starting to 
explain please let me apologize, I'm a newbie in Python and I suspect I'm 
doing something horribly wrong.

I have exposed in Python a C++ class with Boost::Python (in the form of a 
shared object). This class (among other things) reads from a file a list of 
real numbers, and stores them internally as doubles.

What happens is that when using matplotlib my exposed class internally begins 
to treat reals like they were integers. In other words, when reading reals 
from a file they are stored as integers, as can be seen by printing the 
contents of the class to screen: all decimal parts are truncated (i.e., 
3.85000E5 instead of 3.8500052719E5). This is _not_ some kind of 
visualization bug, since my class discards reals whose absolute value is 
(almost) zero and indeed when using matplotlib the class loads fewer "reals" 
from the very same file (in other words, values whose abs is < 1 are seen as 
zeroes and as such they get discarded: all reals whose abs is < 1 are missing 
when using matplotlib).

This is extremely strange to me, since I really don't get how matplotlib can 
influence the internal behaviour of my class. Is there somewhere some 
directive in python that can setup the floating point unit?

The "bug" happens exactly after loading matplotlib, without it everything is 
alright. The C++ code from which the class derives has been tested quite 
thoroughly, so I don't think the problem stems from there.

Any pointer would be greatly appreciated :) Thanks very much,

  Francesco (please CC as I'm not subscribed)

> There are currently no Mac binaries for
> that version on SourceForge or pythonmac.

They're up now.

Russell E Owen wrote:
>> Russell E. Owen wrote:
>>> On Feb 25 Samuel Smith reported that WXAgg crashed on MacOS X using 
>>> matplotlib 0.87. I just built matplotlib 0.87.7 on Python 2.5 and am 
>>> still having the problem.
>>> - matplotlib 0.87.7 (from source)
>>
>> That may be the issue -- are you sure you compiled against the right 
>> wx? Apple delivered a version with OS-X 10.4, and it tends to get 
>> found when you compile. Search the archives here for how to get it to 
>> find the right one.

> I used the wxPython binary installer from pythonmac.org. I assumed it 
> included a statically linked wx library but perhaps it does not.

yes, it does (well, not exactly, but it does include it's own copies of 
the wx libs)

> If not, 
> then I have no idea what wx it's using; I don't remember installing one 
> but I suppose I might have long ago.

However, the issue is not which wx wxPython is using, but which wx 
matplotlib was built against.

> I'm not sure this is relevant, but while building matplotlib I got 
> warnings about using the deprecated wxPython package instead of wx.

yup, that's it all right.

when mpl is building , it looks for a utility called wx-config, that 
tells it where to find the headers and libs it needs. The default 
wx-config on OS-X will point to the wrong wx, so you need to set a n 
environment variable or something pointing to the correct wx-config.

Sorry I don't have the specific details right now, but it should be in 
the archives, or poke through setup.py and associated files for more 
info. I think I put a helpful warning in there at some point.

good luck,

-Chris



  I
> had assumed the matplotlib folks were just a bit behind on their use of 
> wx, but maybe it is a clue as to what's wrong.
> 
> -- Russell


-- 
Christopher Barker, Ph.D.
Oceanographer

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

Chr...@no...