matplotlib-users Mailing List for matplotlib (Page 7)

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

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.

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

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

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

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

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
===============================================================

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

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
))))))))))))))))))))))))))))))))))))))))))))

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

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

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

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 

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-

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

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

Hi,
On Wed, 5 Jan 2005, Ben Vanhaeren wrote:
> Hello,
>
> I'm trying to generate an animated plot embedded in gtk. The problem I have is
> that the plot only gets drawn when the animation loop is finished instead of
> everytime the draw() function is called inside the loop. Is there any other
> way to force the plot to be redrawn ?
From your description I suspect that you have a loop in
a subroutine which does one plot after another. However,
doing it this way does not leave gtk any opportunity to
refresh the corresponding window.
In the example of a moving sine
 http://matplotlib.sourceforge.net/examples/anim.py
John remarks that one has to
"""
# turn interactive mode on for dynamic updates. If you aren't in
# interactive mode, you'll need to use a GUI event handler/timer.
"""
Maybe you can use something from the mov_sin_mpl_gtk.py example,
http://sourceforge.net/mailarchive/forum.php?thread_id=6175425&forum_id=33405
I for myself haven't use embedding in gtk, so maybe someone
else has a working example...
Best,
Arnd

Hello,
I'm trying to generate an animated plot embedded in gtk. The problem I have is 
that the plot only gets drawn when the animation loop is finished instead of 
everytime the draw() function is called inside the loop. Is there any other 
way to force the plot to be redrawn ?
Best regards,
Ben Vanhaeren 

I'm getting confused about meaning of shape parameter
of arrays used in a pcolor plot...
xarray= [ 0. 1.25 2.5 3.75 5. 0. 1.25 2.5 3.75 5.
0. 1.25 2 .5
 3.75 5. 0. 1.25 2.5 3.75 5. ]
yarray= [500 500 500 500 500 600 600 600 600 600 700 700 700 700 700
800 800 800 80 0
 800]
zarray= [...etc.]
This will create a proper pcolor plot with 4 rows and 5 columns
if I set all 3 array 'shapes' to be (4, 5).
What is confusing me is that if I want to SWAP xarray and yarray
in order to create a plot with 5 rows and 4 columns then
I MUST STILL SET 'shapes' TO BE (4,5).
'shapes' OF ARRAYS DOESN'T EQUAL DIMENSIONS OF PLOT!?!?
*This* is what is confusing me. I'm not sure what array 'shape'
means if it doesn't mean (# plot rows, # plot columns).
Any help greatly appreciated.
Sincerely,
Chris
--
_______________________________________
Christian Seberino, Ph.D.
SPAWAR Systems Center San Diego
Code 2872
49258 Mills Street, Room 158
San Diego, CA 92152-5385
U.S.A.
Phone: (619) 553-9973
Fax : (619) 553-6521
Email: seb...@sp...
_______________________________________

pcolor function gives a nice color plot when user supplies
a list of triplets. e.g. [ (1,2,3), (4,5,6), ... ].
I usually try to supply these points such that the points
are in some *order* and on a regular *lattice*.
Are there any issues with supplying points in any random
order that aren't evenly spaced but completely random
in position as well?
Chris
--
_______________________________________
Christian Seberino, Ph.D.
SPAWAR Systems Center San Diego
Code 2872
49258 Mills Street, Room 158
San Diego, CA 92152-5385
U.S.A.
Phone: (619) 553-9973
Fax : (619) 553-6521
Email: seb...@sp...
_______________________________________

Fernando Perez wrote:
> I was getting a 'pygtk present but import failed' message, which I 
> couldn't understand. I modified setup.py to reraise the exception at 
> that point, and it turned out to be a RuntimeError('could not open 
> display') exception.
Yes, I noticed the same thing when I tried to build matplotlib through 
an SSH session which didn't have X forwarding enabled. I get the 
message "pygtk present but import failed
Using default library and include directories for Tcl and Tk because a 
Tk window failed to open. You may need to define DISPLAY for Tk to work 
so that setup can determine where your libraries are located." The code 
is in setupext.py starting at line 198:
 try:
 tk=Tkinter.Tk()
 except Tkinter.TclError:
 print "Using default library and include directories for Tcl and 
Tk because a"
 print "Tk window failed to open. You may need to define DISPLAY 
for Tk to work"
 print "so that setup can determine where your libraries are 
located."
The 'import gtk' at line 149 in setup.py also fails if DISPLAY is not set.

Stephen Walton wrote:
> Happy New Year, Fernando!
> 
> Gee, I can't believe I can answer one of your questions :-)
Well, I'm happy to give you a chance to help :)
> 
>>/usr/include/pygtk-2.0/pygobject.h:140: error: expected `,' or `...' 
>>before "typename"
>>/usr/include/pygtk-2.0/pygobject.h:147: error: expected `,' or `...' 
>>before "typename"
>>error: command 'gcc' failed with exit status 1
> 
> 
> It's a known typo in the referenced two lines in pygobject.h. Until a 
> patch is released, manually change "typename" to "_typename"; it's just 
> in the function prototype so the name doesn't matter.
Ah, many thanks! After fixing this, it all worked great, except for one 
confusing little accident I'll mention in case someone else has the same 
problem.
I was getting a 'pygtk present but import failed' message, which I couldn't 
understand. I modified setup.py to reraise the exception at that point, and 
it turned out to be a RuntimeError('could not open display') exception. Well, 
it happens that I do a lot of my sysadmin work using screen, so that I can 
reattach to a session from anywhere, or leave long-running compiles going. By 
default, screen blocks X11 (I need to learn how to fix this), so the gtk 
initialization was failing due to lack of access to my display, even though 
the library is all there. The fix was to run the bdist_rpm _outside_ of 
screen, but it might be worth changing the setup file so that this error does 
not crash the build. I'm not sure it should really be necessary to have a 
running X11 for the build, as long as all the necessary headers and libraries 
are present.
Anyway, thanks again (and also to Vineet) for the help. You saved me a lot of 
frustration.
Regards,
f

I just spent half a day on this. There should be an entry in the release
notes on this. 
I found a reference to the problem here:
http://www.daa.com.au/pipermail/pygtk/2004-October/008826.html
I downloaded the latest version of pygobject.h and everything worked agains.
Vinjvinj
-----Original Message-----
From: mat...@li...
[mailto:mat...@li...] On Behalf Of Fernando
Perez
Sent: Monday, January 03, 2005 8:33 PM
To: mat...@li...
Subject: [Matplotlib-users] Building on fedora3?
Hi all,
I wonder if anyone is using FedoraCore3. I'd been recently building 
matplotlib RPMs with my Fedora 2 destktop without any troubles (after
patching 
distutils to ignore a multiple RPMs assertion). I just upgraded my desktop
to 
Fedora 3, and now the build fails with:
root@planck[matplotlib-0.70]# python setup.py build
running build
running build_py
running build_ext
building 'matplotlib.backends._gtkagg' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m32 -march=i386 
-mtune=pentium4 -D_GNU_SOURCE -fPIC -fPIC -I/usr/local/include
-I/usr/include 
-Isrc -Iagg22/include -I. -I/usr/local/include -I/usr/include 
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -Isrc/freetype2 
-Iagg22/include/freetype2 -I./freetype2 -I/usr/local/include/freetype2 
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include 
-I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include 
-I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 
-I/usr/include/freetype2/config -I/usr/include/glib-2.0 
-I/usr/lib/glib-2.0/include -I/usr/include/python2.3 -c src/_gtkagg.cpp -o 
build/temp.linux-i686-2.3/src/_gtkagg.o
In file included from /usr/include/python2.3/Python.h:8,
 from /usr/include/pygtk-2.0/pygobject.h:5,
 from src/_gtkagg.cpp:8:
/usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE"
redefined
In file included from /usr/include/string.h:26,
 from 
/usr/lib/gcc/i386-redhat-linux/3.4.2/../../../../include/c++/3.4.2/cstring:5
1,
 from src/_gtkagg.cpp:1:
/usr/include/features.h:150:1: warning: this is the location of the previous
definition
In file included from src/_gtkagg.cpp:8:
/usr/include/pygtk-2.0/pygobject.h:140: error: expected `,' or `...' before 
"typename"
/usr/include/pygtk-2.0/pygobject.h:147: error: expected `,' or `...' before 
"typename"
error: command 'gcc' failed with exit status 1
Does anyone have a hint of what may be going on here? I looked at the 
pygobject.h file, but nothing jumps to my eye as obviously wrong.
Any help would be much appreciated.
Cheers,
f
-------------------------------------------------------
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

Happy New Year, Fernando!
Gee, I can't believe I can answer one of your questions :-)
> /usr/include/pygtk-2.0/pygobject.h:140: error: expected `,' or `...' 
> before "typename"
> /usr/include/pygtk-2.0/pygobject.h:147: error: expected `,' or `...' 
> before "typename"
> error: command 'gcc' failed with exit status 1
It's a known typo in the referenced two lines in pygobject.h. Until a 
patch is released, manually change "typename" to "_typename"; it's just 
in the function prototype so the name doesn't matter.
Best of all, on FC3, 'python setup.py bdist_rpm' works great and 
generates a distributable RPM provided one is mindful of the dependency 
on a statically linked, architecture-specific ATLAS library.
Steve Walton

Hi all,
I wonder if anyone is using FedoraCore3. I'd been recently building 
matplotlib RPMs with my Fedora 2 destktop without any troubles (after patching 
distutils to ignore a multiple RPMs assertion). I just upgraded my desktop to 
Fedora 3, and now the build fails with:
root@planck[matplotlib-0.70]# python setup.py build
running build
running build_py
running build_ext
building 'matplotlib.backends._gtkagg' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m32 -march=i386 
-mtune=pentium4 -D_GNU_SOURCE -fPIC -fPIC -I/usr/local/include -I/usr/include 
-Isrc -Iagg22/include -I. -I/usr/local/include -I/usr/include 
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -Isrc/freetype2 
-Iagg22/include/freetype2 -I./freetype2 -I/usr/local/include/freetype2 
-I/usr/include/freetype2 -I/usr/local/include -I/usr/include 
-I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include 
-I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 
-I/usr/include/freetype2/config -I/usr/include/glib-2.0 
-I/usr/lib/glib-2.0/include -I/usr/include/python2.3 -c src/_gtkagg.cpp -o 
build/temp.linux-i686-2.3/src/_gtkagg.o
In file included from /usr/include/python2.3/Python.h:8,
 from /usr/include/pygtk-2.0/pygobject.h:5,
 from src/_gtkagg.cpp:8:
/usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined
In file included from /usr/include/string.h:26,
 from 
/usr/lib/gcc/i386-redhat-linux/3.4.2/../../../../include/c++/3.4.2/cstring:51,
 from src/_gtkagg.cpp:1:
/usr/include/features.h:150:1: warning: this is the location of the previous 
definition
In file included from src/_gtkagg.cpp:8:
/usr/include/pygtk-2.0/pygobject.h:140: error: expected `,' or `...' before 
"typename"
/usr/include/pygtk-2.0/pygobject.h:147: error: expected `,' or `...' before 
"typename"
error: command 'gcc' failed with exit status 1
Does anyone have a hint of what may be going on here? I looked at the 
pygobject.h file, but nothing jumps to my eye as obviously wrong.
Any help would be much appreciated.
Cheers,
f