matplotlib-users — Discussion related to using matplotlib

Re: [Matplotlib-users] matplotlib / Python 2.4 / Numarray

[John H. <jdh...@ac...>]

>>>>> "Darren" == Darren Dale <dd...@co...> writes:

    Darren> I think the "Installing on Windows" note is out of
    Darren> date. Recently, the MPL dev's changed the install code to
    Darren> automatically detect numarray and Numeric, and to install
    Darren> accordingly. This is why you dont see an installer
    Darren> specifically for numarray or numeric.

Yep, that's right.  Perhaps someone else can verify that matplotlib
with numerux : numarray works on python2.4 / win32 just to verify that
I didn't screw up the 2.4 installer.

    Darren> As for solving your problem, I don't have an answer but
    Darren> let me offer a couple suggestions. Can you import numarray
    Darren> from an interactive python session?  Could you try to
    Darren> temporarily install Numeric, and see if MPL can install?

Also verify that your http://matplotlib.sf.net/.matplotlibrc setting
for numerix  is numarray.  While testing, you may want to run with
--verbose-helpful which may provide some additional diagnoistic
information.  Note you can also select numeric vs numarray from the
DOS shell, which can be helpful while debugging this problem

 c:> python myscript.py --verbose-helpful --Numeric
 c:> python myscript.py --verbose-helpful --numarray

Hope this helps,
JDH

[Matplotlib-users] Memory not released using tkAgg or WXAgg?

[Hennie v. N. <hen...@in...>]

I'm new to both Python and matplotlib.

I'm using this on MS Win with Python 2.3 and matplotlib 0.7. and ipython 
as IDE.

A substantial amount of memory is allocated when a array of constantly 
varying values is plotted, as example:

# Sawtooth signal 32768 elements long to show memory usage.
y = ones(2**15)
y[1::2] = 0
plot(y)

if the figure created is now killed, the memory is not released, and 
more memory is allocated each time the plot() command is executed.  Thr 
memory is only returned to the system once python is closed.

Plotting a signal with less amplitude variation or slow amplitude change 
( for instance plot(ones2**15)   or plot(sin(arange(0,10,10./2**15)) ) 
uses a lot less memory, so the leak is not as obvious, but still there.

Any suggestions from the group on resolving this?

Thanks,
Hennie

Re: [Matplotlib-users] matplotlib / Python 2.4 / Numarray

[Darren D. <dd...@co...>]

Hi Greg,

> Hi folks.  Just setting up a new machine with Python 2.4, and wanted to
> check something.  Under "Installing on Windows", the Matplotlib pages at
> sf.net say:
>
>     For standard python installations, you will also need to install
>     either Numeric or numarray in addition to the matplotlib installer.
>     matplotlib provides installers for Numeric and numarray users. It is
>     important that you pick the matplotlib installer that corresponds to
>     your array package.  Ie, if you mostly work with numarray arrays, use
>     the matplotlib numarray installer. matplotlib has a numerix setting in
>     the matplotlib rc file (which by default resides in
>     c:\python23\share\matplotlitb\.matplotlibrc) and you should make sure
>     this setting corresponds to your preferred array package.
>
> However, the download page:
>
>    
> http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=8247
>4
>
> only differentiates installers by Python version; there's no hint which
> one is for Numpy, numarray, etc.  The one I grabbed
> (matplotlib-0.70.1-win32.py2.4.exe) installed, but complains about not
> being able to find numarray (which is installed, for Python 2.4).  I'd be
> happy to use Numpy, but the only releases available are for Python 2.3.
>
> Any suggestions?
>

I think the "Installing on Windows" note is out of date. Recently, the MPL 
dev's changed the install code to automatically detect numarray and Numeric, 
and to install accordingly. This is why you dont see an installer 
specifically for numarray or numeric.

As for solving your problem, I don't have an answer but let me offer a couple 
suggestions. Can you import numarray from an interactive python session? 
Could you try to temporarily install Numeric, and see if MPL can install?

Darren

[Matplotlib-users] matplotlib / Python 2.4 / Numarray

[Greg W. <gvw...@cs...>]

Hi folks.  Just setting up a new machine with Python 2.4, and wanted to
check something.  Under "Installing on Windows", the Matplotlib pages at
sf.net say:

    For standard python installations, you will also need to install
    either Numeric or numarray in addition to the matplotlib installer.
    matplotlib provides installers for Numeric and numarray users. It is
    important that you pick the matplotlib installer that corresponds to
    your array package.  Ie, if you mostly work with numarray arrays, use
    the matplotlib numarray installer. matplotlib has a numerix setting in
    the matplotlib rc file (which by default resides in
    c:\python23\share\matplotlitb\.matplotlibrc) and you should make sure
    this setting corresponds to your preferred array package.

However, the download page:

    http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474

only differentiates installers by Python version; there's no hint which
one is for Numpy, numarray, etc.  The one I grabbed
(matplotlib-0.70.1-win32.py2.4.exe) installed, but complains about not
being able to find numarray (which is installed, for Python 2.4).  I'd be
happy to use Numpy, but the only releases available are for Python 2.3.

Any suggestions?

Thanks,
Greg Wilson

Re: [Matplotlib-users] Small bug in matplotlib-0.70

[Stephen W. <ste...@cs...>]

Andrew Straw wrote:

> Stephen Walton wrote:
>
>> Line 851 in pylab.py should change from
>>
>>        line = line[:line.rfind('%')].strip()
>>
>> to
>>
>>        line = line[:line.find('%')].strip()
>>
>
> Done.

Cool, thanks.

> Now maybe someone can contribute a patch for 3D plots while John is in 
> Brazil as a sign of our appreciation. :)

Based on what I've read around here, implementing 3D plots is going to 
require more than a simple patch.

[Matplotlib-users] TkAgg memory leak

[Jeffery D. C. <jco...@ea...>]

I noticed a memory leak when using imshow with the TkAgg backend (the 
Agg backend seems to be OK).  Below is the system information and the 
result of running the memory leak script provided in the FAQ.  I use 
Numeric for my work, but numarray is also installed.

localhost:src$ python2.3
Python 2.3.4 (#1, Oct 31 2004, 10:10:53)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import numarray
 >>> numarray.__version__
'1.1'
 >>> import Numeric
N>>> Numeric.__version__
'23.5'
 >>> import pylab
 >>> import matplotlib
 >>> matplotlib.__version__
'0.70.1'

Output from memory leak checker script:

0    52632 17192
1    58484 18679
2    64180 20126
3    70000 21610
4    75772 23009
5    81564 24474
6    87272 25923
7    92988 27372
8    98684 28817
9    104456 30213
10    110160 31662
11    115956 33142
12    121764 34626
13    127468 36008
14    133172 37456
15    138968 38921
16    144748 40385
17    150444 41766
18    156132 43211
19    161816 44657
20    167516 46104
21    173204 47547
22    179008 48966
23    184676 50409
24    190372 51856
25    196060 53300
26    201764 54684
27    207536 56146
28    213240 57594
29    218948 59041
30    224616 60487
31    230288 61866
32    235964 63308
33    241664 64757
34    247444 66219
35    253248 67636
36    259024 69099
37    264712 70544
38    270408 71993
39    276084 73370
40    281780 74817
41    287568 76294
42    293260 77739
43    298960 79185
44    304648 80565
45    310352 82014
46    316100 83470
47    321792 84917
48    327452 86295
49    333236 87775
50    338928 89220
51    344728 90686
52    349444 92103
53    350840 93551
54    341692 95015
55    332648 96494
56    326660 97955
57    327812 99332
58    330168 100774
59    331612 102224
60    333080 103667
61    334524 105048
62    336444 106532
63    338144 107995
64    340060 109454
65    340968 110837
66    339636 112286
67    340340 113725
68    340984 115174
69    343468 116555
70    344244 118001
71    344456 119450
72    346036 120912
73    345808 122377
74    346944 123775
75    348400 125255
76    350128 126717
77    349552 128173
78    348952 129568
79    348036 131014
80    347556 132461
81    349000 133907
82    348828 135288
83    348528 136733
84    348156 138199
85    348420 139639
86    346460 141083
87    349312 142465
88    348832 143926
89    348404 145373
90    349888 146851
91    349780 148229
92    348632 149677
93    348748 151137
94    348040 152619
95    347016 154001
96    347108 155466
97    348496 156905
98    350300 158349
99    351956 159766
100    353368 161212
101    351320 162659
102    353216 164121
103    352952 165569
104    353652 166952
105    353256 168411
106    352088 169873
107    354428 171309
108    353440 172691
109    356004 174173
110    356008 175613
111    354096 177074
112    356036 178458
113    356228 179923
114    358000 181403
115    358012 182847
116    358220 184296
117    359524 185697
118    357732 187143
119    357580 188580
120    355680 190024
121    356336 191433
122    356676 192913
123    358288 194362
124    356352 195808
125    356684 197208
126    357296 198689
127    358940 200155
128    361464 201602
129    360752 203045
130    360148 204462
131    362032 205908
132    364036 207397
133    365656 208836
134    365360 210217
135    361592 211675
136    364828 213122
137    365600 214567
138    365184 215961
139    370880 217425
140    362380 218872
141    366444 220319
142    362832 221785
143    366424 223164
144    363908 224630
145    363980 226076
146    369004 227524
147    371348 228907
148    370072 230353
149    371484 231799
Average memory consumed per loop: 1427.6000k bytes

Thanks!

--
Jeff

[Matplotlib-users] Re: [matplotlib-devel] overridding builtin variables in pylab

[Fernando P. <Fer...@co...>]

Andrew Straw wrote:

> So, I offer the following patch [2] to pylab.py which fixes this. I 
> hereby ask for your feedback indicating if you are happy with the 
> current behavior, or if you prefer that pylab does not override 
> builtins. (Also, if you have a better way, that would be appreciated, too.)

+1 on your patch.

I'd also much rather have the builtin namespace be left alone.

Cheers,

f

[Matplotlib-users] overridding builtin variables in pylab

[Andrew S. <str...@as...>]

A few weeks ago (on Dec 18), I send an email to the matplotlib-devel 
list indicating that "from pylab import *" overrides some builtin 
functions, such as min() and max(). [1]

This results from pylab enlarging its namespace greatly with statements 
like "from numerix import *" and "from mlab import *".  In general this 
is a good thing, but it seems numarray.linear_algebra.mlab (amongst 
possibly others) overrides some builtin names.  Although I don't see the 
benefit in this design for numarray.linear_algebra.mlab, I can live with 
it, since I never do "from numarray.linear_algebra.mlab import *". 

However, I (and many others here, I suspect) would like to frequently 
use "from pylab import *", and it really pisses me off when I discover 
that various builtins are overridden, causing mysterious errors that may 
be hard to track down.

So, I offer the following patch [2] to pylab.py which fixes this. I 
hereby ask for your feedback indicating if you are happy with the 
current behavior, or if you prefer that pylab does not override 
builtins. (Also, if you have a better way, that would be appreciated, too.)

You may check your own systems using a little script I wrote while 
testing this. [3]

Cheers!
Andrew

[1] 
http://sourceforge.net/mailarchive/forum.php?thread_id=6190717&forum_id=36187

[2] Patch to pylab.py, to be inserted anywhere after the last "from blah 
import *", e.g. line 216.

# restore builtin functions which may have been overridden
min = getattr(sys.modules['__builtin__'],'min')
max = getattr(sys.modules['__builtin__'],'max')
sum = getattr(sys.modules['__builtin__'],'sum')
round = getattr(sys.modules['__builtin__'],'round')
abs = getattr(sys.modules['__builtin__'],'abs')

[3] Script to test for overriding of builtin names:

import sys

def check_globals():
    for key in globals().keys():
        if key in dir(sys.modules['__builtin__']):
            if globals()[key] != getattr(sys.modules['__builtin__'],key):
                print "'%s' was overridden in globals()."%key

print 'before pylab import'
check_globals()
print

from pylab import *

print 'after pylab import'
check_globals()
print

[Matplotlib-users] pylab exposing time?

[danny s. <dan...@ya...>]

Howdy,

We just installed matplotlib version 0.70.1 on a new computer, and some
code I wrote broke which was written for matplotlib 0.61. 

The code I used that broke was:

from time import time
from matplotlib.matlab import *

with the later version of matplotlib this became:

from time import time
from matplotlib.pylab import *

and this doesn't work because pylab exposes time as a module. Now I
realize this is not necessarily good programming style :-). But I am
using  about 20 different pylab commands. So the question is, should
pylab be more careful about what it exposes?

thanks,
Danny 



		
__________________________________ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com 

Re: [Matplotlib-users] Small bug in matplotlib-0.70

[Andrew S. <str...@as...>]

Stephen Walton wrote:

> At my request, John Hunter put a feature in the 'load' subroutine in 
> Pylab which treats everything after a '%' sign as a comment.  This 
> makes it more compatible with MATLAB (tm);  I use this feature to 
> comment files which would otherwise be simple lists of numbers.  
> However, there is a small bug.  Line 851 in pylab.py should change from
>
>        line = line[:line.rfind('%')].strip()
>
> to
>
>        line = line[:line.find('%')].strip()
>
> since everything after a '%' sign should be treated as a comment.  
> This bit me when I had a comment line where the comment itself 
> included a % sign.

Done.

Now maybe someone can contribute a patch for 3D plots while John is in 
Brazil as a sign of our appreciation. :)

Cheers!
Andrew

[Matplotlib-users] Small bug in matplotlib-0.70

[Stephen W. <ste...@cs...>]

At my request, John Hunter put a feature in the 'load' subroutine in 
Pylab which treats everything after a '%' sign as a comment.  This makes 
it more compatible with MATLAB (tm);  I use this feature to comment 
files which would otherwise be simple lists of numbers.  However, there 
is a small bug.  Line 851 in pylab.py should change from

        line = line[:line.rfind('%')].strip()

to

        line = line[:line.find('%')].strip()

since everything after a '%' sign should be treated as a comment.  This 
bit me when I had a comment line where the comment itself included a % sign.

Re: [Matplotlib-users] starting up

[Andrew S. <str...@as...>]

Maarten de Vries wrote:

>Hello,
>The best wishes for the new year to all of you!
>I am completely new to this part of the game. I have worked with Python and 
>Matlab and the matplotlib appears to be an excellent tool for my demands, but 
>I cannot get the thing working. I have spend two days to try to find my own 
>way out of it, but that didn't work, so I will ask your help.
>I have a SuSE Linux 9.2 i386 installation. I have changed the prefix and 
>exec-prefix in setupext.py to read '/usr' and start the build routine to get:
>maarten@cleopatra:~/Documents/Downloads/matplotlib-0.70.1> python setup.py 
>build
>sh: pkg-config: command not found
>sh: pkg-config: command not found
>sh: pkg-config: command not found
>sh: pkg-config: command not found
>  
>
<snipped further output>

I'd install pkg-config before going any further.  I believe it will find 
dependencies automatically without relying on you to enter them.  
Unfortunately, I have no idea how to install it on SuSE.

Your later errors indicate problems finding the GTK header files, which 
I think pkg-config will help with.  (At least once you install them, too!)

Cheers!
Andrew

Re: [Matplotlib-users] Using color in fill

[Perry G. <pe...@st...>]

Yes, colormaps are callable so you can call the colormap with either a 
scalar value or an
array of values and what will be returned is a tuple of rgba values or 
an array (shape
= 4, nelements). See the docstring on __call__ for 
LinearSegmentedColormap in colors.py

Perry

On Jan 6, 2005, at 3:18 PM, Carol Leger wrote:

> I am using fill to make filled polygons.  I want to fill the polygons 
> with colors that reflect data values, similar to what imshow does.
>
> Is there a way to extract the rgb tuples from a Colormap? This could 
> be an array of N tuples, each tuple containing 3 0-1 floats that 
> describe the color or three separate arrays, one each for red, green 
> and blue.
>
> I made the mistake of using some non-public attributes of the class 
> colorMap to accomplish this in a previous version of matplotlib.  That 
> was a mistake since Colormap._red_lut, Colormap._green_lut and 
> Colormap._blue_lut no longer exist.
>
> Once I have the array of tuples, I can determine which one I want and 
> create a hex string using rgb2hex to get a color suitable for use with 
> fill.
>
> I need the flexability to make the same plot using several different 
> color maps.
> -- 
> Ms. Carol A. Leger
> SRI International			Phone: (650) 859-4114
> 333 Ravenswood Avenue G-273
> Menlo Park, CA 94025                    e-mail: le...@sr...
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

[Matplotlib-users] starting up

[Maarten de V. <mh....@qu...>]

Thank you all for helping me out! As far as I can see at the moment I have got 
the beast moving. All three suggestions did pay off, so there was not one 
solution. Maybe it is good for other newbies and for future improvements to 
explicit the problems I had:
-- the number of prerequisite libraries, that I had checked on the 
installation instructions page, was not adequate. Maybe if I had installed my 
system as a development-system from the start, it would have been sufficient, 
but now there is a lot of ambiquity in the names of all the required 
components.
-- the pkg-config was nowhere to be found on my system, because it is named 
pkgconfig in YAST.
-- adding some extra libraries for the gtk-components in the build-ext is not 
easily cooked up by a beginner.

I am very happy, that the operation succeeded and I hope that I can have a lot 
of fun with the toolkit. The above considerations are not meant as 
complaining, but only as constructive report.

Thanx again.

 Maarten

[Matplotlib-users] Using color in fill

[Carol L. <car...@sr...>]

I am using fill to make filled polygons.  I want to fill the polygons 
with colors that reflect data values, similar to what imshow does.

Is there a way to extract the rgb tuples from a Colormap? This could be 
an array of N tuples, each tuple containing 3 0-1 floats that describe 
the color or three separate arrays, one each for red, green and blue.

I made the mistake of using some non-public attributes of the class 
colorMap to accomplish this in a previous version of matplotlib.  That 
was a mistake since Colormap._red_lut, Colormap._green_lut and 
Colormap._blue_lut no longer exist.

Once I have the array of tuples, I can determine which one I want and 
create a hex string using rgb2hex to get a color suitable for use with fill.

I need the flexability to make the same plot using several different 
color maps.
-- 
Ms. Carol A. Leger
SRI International			Phone: (650) 859-4114
333 Ravenswood Avenue G-273
Menlo Park, CA 94025                    e-mail: le...@sr...

[Matplotlib-users] problem with 'preserve' aspect in imshow

[Eric E. <ems...@ob...>]

Hi,

is there any suggestion as how to correct the bug in imshow
for the display in mode ''preserve'' (something I explained in
a previous email and that someone else bumped into).
Any input welcome!

thanks and cheers,

Eric

-- 
===============================================================
Observatoire de Lyon                 ems...@ob...
9 av. Charles-Andre                      tel: +33 4 78 86 83 84
69561 Saint-Genis Laval Cedex            fax: +33 4 78 86 83 86
France               http://www-obs.univ-lyon1.fr/eric.emsellem
===============================================================

Re: [Matplotlib-users] custom colormap

[Perry G. <pe...@st...>]

On Jan 5, 2005, at 7:41 AM, Randy Heiland wrote:

> Apologies, but as usual, I'm under a bit of pressure to display a 
> pcolor
> using a custom colormap and it's not intuitively obvious how to do it 
> (but
> I'll keep looking).  If there's a kind soul out there who can quickly 
> point
> me/show me how, I'd appreciate it.  In my simple example, I want to 
> have
> just 4 bands of color:  2 shades of blue for all negative scalar 
> values and
> 2 shades of red for all positive values.
>
> thanks, Randy
>
I responded to this off list (through a separate request). I did want to
point out that the data structure used to create linear segmented 
colormaps
does provide the capability for easily defining constant color bands. 
There
is a simple, but not very general, means of just restricting the number 
of
points in the color map. By making this a small number, one will just 
have
that many distinct colors available (by default it is set to 256, which
generally makes it hard to distinguish the distinct levels). This is 
only
useful if you wish the thresholds for the constant levels to be 
uniformly
spaced between 0 and 1 after normalizing the data values to that 
interval.
In this particular case choosing N to be small (7) didn't align 0 with 
one
of these thresholds and thus wasn't useful for this purpose.

The more general means of setting arbitrary constant color bands is to 
take
advantage of the fact that the definition of the linear segments allows 
for
discontinuities at each threshold. Two examples are shown below. The 
first
is a continuous colormap and the second illustrates use of constant 
color
bands.

The data structure is simply dictionary that has entries for each of 
the 3
colors. Each of these is set a tuple of tuples. Each of the interior 
tuples
represents the color value(s) at a normalized data value (i.e., values 
ranging
from 0 to 1). The first value is the normalized data value for which the
color intensities apply. Two color intensities are required to allow for
discontinuities. So the second value of the tuple is the color intensity
just below the data value, and the third the value is the value just 
above.
If the color map is to be continuous at that point, these two values 
should
be the same. The tuples should be monotonic in data values and should 
start
with 0. and end with 1. The color intensities are linearly interpolated
between the specified data points. (Actually, color lookup tables are 
generated
instead and simple value lookup is used. As mentioned, the default 
number of
entries in the lookup tables is 256. This can be overridden by 
specifying
how many levels are desired) The following examples illustrate two 
simple cases.

mycmdata1 = {
     'red'  :  ((0., 0., 0.), (0.5, 0.9, 0.9), (1., 1., 1.)),
     'green':  ((0., 0., 0.), (1., 0., 0.)),
     'blue' :  ((0., 0., 0.), (1., 0., 0.))
   }
mycm1 =  LinearSegmentedColormap('mycm',  mycmdata1)

This color map is intended to show only red with values between 0 and 
0.5 using
90% of the red color range, values running from 0.5 to 1.0 only result 
in a
minor increase of the red intensity from 0.9 to 1.0.

mycmdata2 = {
     'red'  :  ((0., 1., 1.), (0.1, 1., 0.), (1., 0., 0.)),
     'green':  ((0., 0., 0.), (0.1, 0., 1.), (0.9, 1., 0.), (1., 0., 
0.)),
     'blue' :  ((0., 0., 0.), (0.9, 0., 1.), (1., 1., 1.))
   }
mycm2 =  LinearSegmentedColormap('mycm',  mycmdata2)

For this color map, value between 0. and 0.1 will be full red, values 
between
0.1 and 0.9 will be full green, and values between 0.9 and 1. will be 
full blue.
Note that in this case the difference in the 2nd and 3rd values in the 
tuples
at the changes in color. Color values are interpolated between the 
normalized
data values and since they are the same over the interval, they are 
constant.

Randy's case is a bit unusual in that one needs to figure out where 0 
in the
original data maps to the normalized data, and then construct a 
colormap that
used that "normalized" 0 value as a threshold. So one must construct a 
colormap
for each such image (admittedly a bit clumsy).

Perry

Re: [Matplotlib-users] starting up

[Cory D. <cd...@st...>]

Hi Maarten

Try 

python setup.py build_ext --include-dir=<directory where you will find
pygobject.h>:<directory where you will find pygtk>

If this works finish the build with python setup.py build.

hope this helps,

Cheers,
Cory.

On Thu, 2005-01-06 at 12:08, Maarten de Vries wrote:
> Hello,
> The best wishes for the new year to all of you!
> I am completely new to this part of the game. I have worked with Python and 
> Matlab and the matplotlib appears to be an excellent tool for my demands, but 
> I cannot get the thing working. I have spend two days to try to find my own 
> way out of it, but that didn't work, so I will ask your help.
> I have a SuSE Linux 9.2 i386 installation. I have changed the prefix and 
> exec-prefix in setupext.py to read '/usr' and start the build routine to get:
> maarten@cleopatra:~/Documents/Downloads/matplotlib-0.70.1> python setup.py 
> build
> sh: pkg-config: command not found
> sh: pkg-config: command not found
> sh: pkg-config: command not found
> sh: pkg-config: command not found
> running build
> running build_py
> creating build
> creating build/lib.linux-i686-2.3
> copying lib/pylab.py -> build/lib.linux-i686-2.3
> creating build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/patches.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/numerix.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/_image.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/colors.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/transforms.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/finance.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/dates.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/cm.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/windowing.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/pyparsing.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/collections.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/na_imports.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/legend.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/text.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/afm.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/mlab.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/matlab.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/figure.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/table.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/_transforms.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/nc_imports.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/font_manager.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/image.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/backend_bases.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/cbook.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/_pylab_helpers.py -> 
> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/pylab.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/_mathtext_data.py -> 
> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/mathtext.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/ticker.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/axes.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/axis.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/__init__.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/artist.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/_contour.py -> build/lib.linux-i686-2.3/matplotlib
> copying lib/matplotlib/lines.py -> build/lib.linux-i686-2.3/matplotlib
> creating build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_cairo.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_template.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_agg.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_gdk.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_gtk.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_wxagg.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_svg.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_tkagg.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_gtkagg.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/__init__.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_fltkagg.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_gd.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_paint.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_ps.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_wx.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/tkagg.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> copying lib/matplotlib/backends/backend_gtkcairo.py -> 
> build/lib.linux-i686-2.3/matplotlib/backends
> running build_ext
> building 'matplotlib._nc_transforms' extension
> creating build/temp.linux-i686-2.3
> creating build/temp.linux-i686-2.3/src
> creating build/temp.linux-i686-2.3/CXX
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
> -fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
> CXX/IndirectPythonInterface.cxx -o 
> build/temp.linux-i686-2.3/CXX/IndirectPythonInterface.o -DNUMERIC=1
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
> -fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
> CXX/cxxsupport.cxx -o build/temp.linux-i686-2.3/CXX/cxxsupport.o -DNUMERIC=1
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
> -fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
> src/_nc_transforms.cpp -o build/temp.linux-i686-2.3/src/_nc_transforms.o 
> -DNUMERIC=1
> In file included from /usr/include/python2.3/Python.h:8,
>                  from CXX/Objects.hxx:9,
>                  from CXX/Extensions.hxx:18,
>                  from src/_transforms.h:10,
>                  from src/_nc_transforms.cpp:2:
> /usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined
> In file included from /usr/include/g++/i586-suse-linux/bits/os_defines.h:39,
>                  from /usr/include/g++/i586-suse-linux/bits/c++config.h:35,
>                  from /usr/include/g++/functional:53,
>                  from src/_nc_transforms.cpp:1:
> /usr/include/features.h:132:1: warning: this is the location of the previous 
> definition
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
> -fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
> CXX/cxxextensions.c -o build/temp.linux-i686-2.3/CXX/cxxextensions.o 
> -DNUMERIC=1
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
> -fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
> src/mplutils.cpp-o build/temp.linux-i686-2.3/src/mplutils.o -DNUMERIC=1
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
> -fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
> CXX/cxx_extensions.cxx -o build/temp.linux-i686-2.3/CXX/cxx_extensions.o 
> -DNUMERIC=1
> g++ -pthread -shared build/temp.linux-i686-2.3/src/_nc_transforms.o 
> build/temp.linux-i686-2.3/src/mplutils.o 
> build/temp.linux-i686-2.3/CXX/cxx_extensions.obuild/temp.linux-i686-2.3/CXX/cxxsupport.o 
> build/temp.linux-i686-2.3/CXX/IndirectPythonInterface.o 
> build/temp.linux-i686-2.3/CXX/cxxextensions.o -lstdc++ -lm -o 
> build/lib.linux-i686-2.3/matplotlib/_nc_transforms.so
> building 'matplotlib.backends._gtkagg' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
> -fmessage-length=0 -Wall -fPIC -I/usr/include -I/usr/include -Isrc 
> -Iagg22/include -I. -I/usr/include -I/usr/include -I/usr/include/freetype2 
> -I/usr/include/freetype2 -Isrc/freetype2 -Iagg22/include/freetype2 
> -I./freetype2 -I/usr/include/freetype2 -I/usr/include/freetype2 
> -I/usr/include -I/usr/include -I/usr/include/python2.3 -c src/_gtkagg.cpp -o 
> build/temp.linux-i686-2.3/src/_gtkagg.o
> src/_gtkagg.cpp:8:23: pygobject.h: Onbekend bestand of map
> src/_gtkagg.cpp:9:25: pygtk/pygtk.h: Onbekend bestand of map
> In file included from /usr/include/python2.3/Python.h:8,
>                  from CXX/Objects.hxx:9,
>                  from CXX/Extensions.hxx:18,
>                  from src/_backend_agg.h:8,
>                  from src/_gtkagg.cpp:11:
> /usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined
> In file included from /usr/include/string.h:26,
>                  from /usr/include/g++/cstring:51,
>                  from src/_gtkagg.cpp:1:
> /usr/include/features.h:132:1: warning: this is the location of the previous 
> definition
> src/_gtkagg.cpp: In member function `Py::Object 
> _gtkagg_module::agg_to_gtk_drawable(const Py::Tuple&)':
> src/_gtkagg.cpp:35: error: `PyGObject' undeclared (first use this function)
> src/_gtkagg.cpp:35: error: (Each undeclared identifier is reported only once 
> for each function it appears in.)
> src/_gtkagg.cpp:35: error: `py_drawable' undeclared (first use this function)
> src/_gtkagg.cpp:35: error: syntax error before `;' token
> src/_gtkagg.cpp:39: error: `GdkDrawable' undeclared (first use this function)
> src/_gtkagg.cpp:39: error: `drawable' undeclared (first use this function)
> src/_gtkagg.cpp:39: error: `GDK_DRAWABLE' undeclared (first use this function)
> src/_gtkagg.cpp:40: error: `GdkGC' undeclared (first use this function)
> src/_gtkagg.cpp:40: error: `gc' undeclared (first use this function)
> src/_gtkagg.cpp:40: error: `gdk_gc_new' undeclared (first use this function)
> src/_gtkagg.cpp:48: error: `GDK_RGB_DITHER_NORMAL' undeclared (first use this 
> function)
> src/_gtkagg.cpp:50: error: `gdk_draw_rgb_32_image' undeclared (first use this 
> function)
> src/_gtkagg.cpp: In function `void init_gtkagg()':
> src/_gtkagg.cpp:62: error: `init_pygobject' undeclared (first use this 
> function)
> src/_gtkagg.cpp:63: error: `init_pygtk' undeclared (first use this function)
> error: command 'gcc' failed with exit status 1
> 
> There are two lines in Dutch, meaning 'unknown file or directory' some 20 
> lines from the bottom, for pygobject.h and pygtk/pygtk.h, both in gtkagg.cpp. 
> 
> Could someone please give me a hand?
> 
> Regards,
> 
> Maarten de Vries
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 
))))))))))))))))))))))))))))))))))))))))))))
Cory Davis
Meteorology
School of GeoSciences
University of Edinburgh
King's Buildings
EDINBURGH EH9 3JZ

ph: +44(0)131 6505092
fax +44(0)131 6505780
cd...@st...
co...@me...
http://www.geos.ed.ac.uk/contacts/homes/cdavis
))))))))))))))))))))))))))))))))))))))))))))

[Matplotlib-users] starting up

[Maarten de V. <mh....@qu...>]

Hello,
The best wishes for the new year to all of you!
I am completely new to this part of the game. I have worked with Python and 
Matlab and the matplotlib appears to be an excellent tool for my demands, but 
I cannot get the thing working. I have spend two days to try to find my own 
way out of it, but that didn't work, so I will ask your help.
I have a SuSE Linux 9.2 i386 installation. I have changed the prefix and 
exec-prefix in setupext.py to read '/usr' and start the build routine to get:
maarten@cleopatra:~/Documents/Downloads/matplotlib-0.70.1> python setup.py 
build
sh: pkg-config: command not found
sh: pkg-config: command not found
sh: pkg-config: command not found
sh: pkg-config: command not found
running build
running build_py
creating build
creating build/lib.linux-i686-2.3
copying lib/pylab.py -> build/lib.linux-i686-2.3
creating build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/patches.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/numerix.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/_image.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/colors.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/transforms.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/finance.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/dates.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/cm.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/windowing.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/pyparsing.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/collections.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/na_imports.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/legend.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/text.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/afm.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/mlab.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/matlab.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/figure.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/table.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/_transforms.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/nc_imports.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/font_manager.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/image.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/backend_bases.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/cbook.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/_pylab_helpers.py -> 
build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/pylab.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/_mathtext_data.py -> 
build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/mathtext.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/ticker.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/axes.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/axis.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/__init__.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/artist.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/_contour.py -> build/lib.linux-i686-2.3/matplotlib
copying lib/matplotlib/lines.py -> build/lib.linux-i686-2.3/matplotlib
creating build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_cairo.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_template.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_agg.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_gdk.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_gtk.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_wxagg.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_svg.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_tkagg.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_gtkagg.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/__init__.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_fltkagg.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_gd.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_paint.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_ps.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_wx.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/tkagg.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
copying lib/matplotlib/backends/backend_gtkcairo.py -> 
build/lib.linux-i686-2.3/matplotlib/backends
running build_ext
building 'matplotlib._nc_transforms' extension
creating build/temp.linux-i686-2.3
creating build/temp.linux-i686-2.3/src
creating build/temp.linux-i686-2.3/CXX
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
-fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
CXX/IndirectPythonInterface.cxx -o 
build/temp.linux-i686-2.3/CXX/IndirectPythonInterface.o -DNUMERIC=1
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
-fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
CXX/cxxsupport.cxx -o build/temp.linux-i686-2.3/CXX/cxxsupport.o -DNUMERIC=1
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
-fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
src/_nc_transforms.cpp -o build/temp.linux-i686-2.3/src/_nc_transforms.o 
-DNUMERIC=1
In file included from /usr/include/python2.3/Python.h:8,
                 from CXX/Objects.hxx:9,
                 from CXX/Extensions.hxx:18,
                 from src/_transforms.h:10,
                 from src/_nc_transforms.cpp:2:
/usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined
In file included from /usr/include/g++/i586-suse-linux/bits/os_defines.h:39,
                 from /usr/include/g++/i586-suse-linux/bits/c++config.h:35,
                 from /usr/include/g++/functional:53,
                 from src/_nc_transforms.cpp:1:
/usr/include/features.h:132:1: warning: this is the location of the previous 
definition
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
-fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
CXX/cxxextensions.c -o build/temp.linux-i686-2.3/CXX/cxxextensions.o 
-DNUMERIC=1
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
-fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
src/mplutils.cpp-o build/temp.linux-i686-2.3/src/mplutils.o -DNUMERIC=1
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
-fmessage-length=0 -Wall -fPIC -Isrc -I. -I/usr/include/python2.3 -c 
CXX/cxx_extensions.cxx -o build/temp.linux-i686-2.3/CXX/cxx_extensions.o 
-DNUMERIC=1
g++ -pthread -shared build/temp.linux-i686-2.3/src/_nc_transforms.o 
build/temp.linux-i686-2.3/src/mplutils.o 
build/temp.linux-i686-2.3/CXX/cxx_extensions.obuild/temp.linux-i686-2.3/CXX/cxxsupport.o 
build/temp.linux-i686-2.3/CXX/IndirectPythonInterface.o 
build/temp.linux-i686-2.3/CXX/cxxextensions.o -lstdc++ -lm -o 
build/lib.linux-i686-2.3/matplotlib/_nc_transforms.so
building 'matplotlib.backends._gtkagg' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mcpu=i686 
-fmessage-length=0 -Wall -fPIC -I/usr/include -I/usr/include -Isrc 
-Iagg22/include -I. -I/usr/include -I/usr/include -I/usr/include/freetype2 
-I/usr/include/freetype2 -Isrc/freetype2 -Iagg22/include/freetype2 
-I./freetype2 -I/usr/include/freetype2 -I/usr/include/freetype2 
-I/usr/include -I/usr/include -I/usr/include/python2.3 -c src/_gtkagg.cpp -o 
build/temp.linux-i686-2.3/src/_gtkagg.o
src/_gtkagg.cpp:8:23: pygobject.h: Onbekend bestand of map
src/_gtkagg.cpp:9:25: pygtk/pygtk.h: Onbekend bestand of map
In file included from /usr/include/python2.3/Python.h:8,
                 from CXX/Objects.hxx:9,
                 from CXX/Extensions.hxx:18,
                 from src/_backend_agg.h:8,
                 from src/_gtkagg.cpp:11:
/usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined
In file included from /usr/include/string.h:26,
                 from /usr/include/g++/cstring:51,
                 from src/_gtkagg.cpp:1:
/usr/include/features.h:132:1: warning: this is the location of the previous 
definition
src/_gtkagg.cpp: In member function `Py::Object 
_gtkagg_module::agg_to_gtk_drawable(const Py::Tuple&)':
src/_gtkagg.cpp:35: error: `PyGObject' undeclared (first use this function)
src/_gtkagg.cpp:35: error: (Each undeclared identifier is reported only once 
for each function it appears in.)
src/_gtkagg.cpp:35: error: `py_drawable' undeclared (first use this function)
src/_gtkagg.cpp:35: error: syntax error before `;' token
src/_gtkagg.cpp:39: error: `GdkDrawable' undeclared (first use this function)
src/_gtkagg.cpp:39: error: `drawable' undeclared (first use this function)
src/_gtkagg.cpp:39: error: `GDK_DRAWABLE' undeclared (first use this function)
src/_gtkagg.cpp:40: error: `GdkGC' undeclared (first use this function)
src/_gtkagg.cpp:40: error: `gc' undeclared (first use this function)
src/_gtkagg.cpp:40: error: `gdk_gc_new' undeclared (first use this function)
src/_gtkagg.cpp:48: error: `GDK_RGB_DITHER_NORMAL' undeclared (first use this 
function)
src/_gtkagg.cpp:50: error: `gdk_draw_rgb_32_image' undeclared (first use this 
function)
src/_gtkagg.cpp: In function `void init_gtkagg()':
src/_gtkagg.cpp:62: error: `init_pygobject' undeclared (first use this 
function)
src/_gtkagg.cpp:63: error: `init_pygtk' undeclared (first use this function)
error: command 'gcc' failed with exit status 1

There are two lines in Dutch, meaning 'unknown file or directory' some 20 
lines from the bottom, for pygobject.h and pygtk/pygtk.h, both in gtkagg.cpp. 

Could someone please give me a hand?

Regards,

Maarten de Vries

Re: [Matplotlib-users] GTKAgg Animation Stuck

[Steve C. <ste...@ya...>]

On Wed, 2005-01-05 at 18:35 -0500, Carson Reynolds wrote:
> Greetings,
> 
> I've been trying to build a "stripchart" with matplotlib as part of a 
> larger PyGTK application. I have rebuilt one of the examples as a GTK 
> window class, but it doesn't seem to update unless it is resized. Any ideas?
> 
> Thanks,
> 
> -carson-
The problem is with "import pylab" and mixing pylab commands with the
matplotlib class interface. If you are embedding matplotlib into a PyGTK
application I recommend avoiding pylab completely and using the
matplotlib classes only.

Here's a version of the script where the updates are working.
Regards
Steve

[Matplotlib-users] Clip_on not being set

[Edward A. <Edw...@da...>]

It took me a while to work out how to stop my lines getting clipped at
the axes edges (this is especially troublesome for lines that run along
an axis as the half that falls outside the axis gets clipped, as do the
marker symbols)
=20
Anyway, have a look at the following snippet (I am uing the WXAgg
backend, and have imported pylab):
>>> p =3D plot([1,2,3], color =3D 'r', clip_on =3D False)
>>> p[0].get_color()   #is set as expected
'r'
>>> p[0].get_clip_on()  # should be False, but is True
True
>>> p[0].set_clip_on(False)  #Can be set manually
>>> p[0].get_clip_on()
False
>>>
=20
At present, the clip_on property needs to be set manually, rather than
from within the plot command
Cheers,

Ed
=20

[Matplotlib-users] FigureCanvas widget

[Simon B. <si...@ar...>]

Hi,

I'd like to augment the canvas plot to include mouse drawing facilities. 
Has anyone done something like this ? It would involve adding a toolbar 
to the frame (eg. paint tool selection), and managing the graphics 
primatives (like the Tk canvas). I can see how to hook into the 
underlying backend widget, but it's not so clear the interface for 
adding/removeing graphics objects (points/lines etc.) from the plot.

Any help much appreciated.

Simon.

-- 
Simon Burton, B.Sc.
Licensed PO Box 8066
ANU Canberra 2601
Australia
Ph. 61 02 6249 6940
http://arrowtheory.com 

[Matplotlib-users] GTKAgg Animation Stuck

[Carson R. <ca...@me...>]

Greetings,

I've been trying to build a "stripchart" with matplotlib as part of a 
larger PyGTK application. I have rebuilt one of the examples as a GTK 
window class, but it doesn't seem to update unless it is resized. Any ideas?

Thanks,

-carson-

[Matplotlib-users] custom colormap

[Randy H. <he...@in...>]

Apologies, but as usual, I'm under a bit of pressure to display a pcolor
using a custom colormap and it's not intuitively obvious how to do it (but
I'll keep looking).  If there's a kind soul out there who can quickly point
me/show me how, I'd appreciate it.  In my simple example, I want to have
just 4 bands of color:  2 shades of blue for all negative scalar values and
2 shades of red for all positive values.

thanks, Randy

Re: [Matplotlib-users] ANN: matplotlib-0.65.1

[Perry G. <pe...@st...>]

On Jan 3, 2005, at 7:36 PM, Stephen Walton wrote:

> Stephen Walton wrote:
>
>> second would be a windowed, scrollable view into an image which is 
>> larger than the physical display.
>
> Actually, imshow seems almost to do this.  I did
>
> imshow(imdata,interpolation='nearest')
>
> where imdata was a 1024 square image.  Zooming and panning _seems_ to 
> show the full resolution image with individual pixels visible at high 
> zooms.  Is this right?
>
Since John is away, if I interpret your question correctly, yes. Both 
implot and figimage save a reference to the original image so that when 
redisplayed, it is possible to do things like that (like expanding the 
size of a figimage window will show all pixels previously falling 
outside the bounds).

Your previous request regarding adding scrollable plot regions raises 
an interesting issue. I think this is tricky (John may prove me wrong 
on this). It was this sort of functionality that made chaco 
comparatively complex so I'm hesitant about adding it. Effectively one 
now one would be wandering into the area of having the plotting package 
begin to emulate widgets within its canvas (e.g., the scroll bars).

This doesn't mean that one couldn't write a gui application that had 
scroll bars that responded to scroll events by redisplaying the image 
(and plot) according to their position. But then it becomes gui 
dependent. Paul Barrett's suggestion to do a DS9 clone would likely 
take this approach I think.

As you noticed, the general toolbar gives some of this functionality, 
but I don't know if will satisfy all such needs that something like DS9 
does.

Perry