matplotlib-users Mailing List for matplotlib (Page 2)

When I do the "python setup.py build" on cygwin I get the following =
error:

Traceback (most recent call last):
    File "setup.py", line 164, in ?
        build_transforms(ext_modules, packages, NUMERIX)
    File "/usr/libpython2.4/site-packages/matplotlib-0.84/setupext.py", =
line 655,
in build_transforms
        add_base_flags(module)
    File "/usr/libpython2.4/site-packages/matplotlib-0.84/setupext.py", =
line 100,
in add_base_flage
        incdirs =3D [os.path.join(p, 'include') for p in basedir[sys, =
platform]
KeyError: 'cygwin'

How do I fix this? I installed numarray and I changed the NUMERIX value =
in the matplotlibrc file from Numeric to numarray but I still have the =
same problem.

I am trying to build matplotlib 0.84 on my Linux box:  python 2.2, 
Redhat 3.2.3-53, gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-53)

The error I got is listed below - I am at a loss as to what is up. I 
have built 0.84 with no problem on my OS X machine.
The point in the code indicated by the error is just after a #if / else 
checking whether Numeric of Numarray is present. I have only Numeric on 
this machine and the error occurs just after the #else indicating 
Numeric is present.
My OS X box has numarray, so I guess this branch of code is not hit 
when I compile there.
I did comment out the py-modules line as suggested in the setup.py 
since I am using python 2.2.

Thanks for any help.

--Jim

The error:

building 'matplotlib._nc_cntr' extension
cc -DNDEBUG -O -fPIC -I/usr/local/include -I/usr/include 
-I/export/cdat/cdat-3.3/include/python2.2 -c src/_nc_cntr.c -o 
build/temp.linux-i686-2.2/_nc_cntr.o -DNUMERIC=1
src/_nc_cntr.c:1718: syntax error before "init_nc_cntr"
error: command 'cc' failed with exit status 1

Xavier Gnata ha scritto:
> I'm appy to learn there is a matplotlib package in sid :)
> I have 2 questions (but I'm not sure i'm asking the good person. Are you
> the mainteaner?) :

yes, I am the maintainer

> 1) Could you please also package it for python2.4 ?

It is packaged *also* for python2.4:
http://packages.debian.org/unstable/python/python2.4-matplotlib

> 2) What about the documentation? I know there are problems with pydoc
> (for instance, pyoc need X wich cause problems on the build dd). Maybe
> epydoc could do the job.

this is in my TODO, I'm testing pydoc for now and there are good possibility to
re-include python-matplotlib-doc


-- 
/Vittorio Palmisano/
Home Page: http://redclay.altervista.org

Vittorio Palmisano wrote:

>Hi all,
>matplotlib is now on Debian Unstable:
>http://packages.debian.org/unstable/python/python-matplotlib
>
>should work also with Debian Sarge adding this line to /etc/apt/sources.list:
>deb http://ftp.it.debian.org/debian/ unstable main
>
>thanks to Marco Presi for upload :)
>
>
>  
>
Hi,

I'm appy to learn there is a matplotlib package in sid :)
I have 2 questions (but I'm not sure i'm asking the good person. Are you 
the mainteaner?) :
1) Could you please also package it for python2.4 ?
2) What about the documentation? I know there are problems with pydoc 
(for instance, pyoc need X wich cause problems on the build dd). Maybe 
epydoc could do the job.

Xavier

Hi all,
matplotlib is now on Debian Unstable:
http://packages.debian.org/unstable/python/python-matplotlib

should work also with Debian Sarge adding this line to /etc/apt/sources.list:
deb http://ftp.it.debian.org/debian/ unstable main

thanks to Marco Presi for upload :)


-- 
/Vittorio Palmisano/
Home Page: http://redclay.altervista.org

Ryan Krauss wrote:
> Sorry to make more work for you.  Yes, turning off the accelerator
> gets rid of the seg fault:

That's what I was afraid of hearing.  I haven't been able to reproduce this 
under Debian Sarge or Sid.

> Let me know what to try next.  Another strace?

I'm not sure that an strace will help too much.  I probably need the segfault 
stacktrace, which you can get by attaching GDB to the Python process.  Please 
let me know if I shoudl send you instructions.

Also, please check that your system configuration is comparable to my Sid 
environment, which is:

  Python:     2.3.5
  IPython:    0.6.15
  wxPython:   2.6.1.2pre
  matplotlib: 0.85cvs

Finally, please double-triple-extra check that your wxPython header files 
correspond exactly to the version of wxPython you are using.  If they don't, 
then all bets are off.

Ken

Christian Meesters wrote:
> I remembered that there was a recent post on installing matplotlib on
> Ubuntu.
> 
> I tried apt-get update without an error message, but running apt-get
> install python-matplotlib-jdh gives me the following output.
> 
> Reading package lists... Done
> Building dependency tree... Done
> Package python-matplotlib-jdh is not available, but is referred to by
> another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> E: Package python-matplotlib-jdh has no installation candidate

Are you using John's CVS packages or the stable-version packages at 
anakonda.net?  It sounds like this might just be a matter of tweaking 
`/etc/apt/sources.list' appropriately, assuming we can figure out what the 
problem is.

Ken

Ryan Krauss wrote:
> The only way around the wx-config error is to download the wxPython
> source tarball and find wxPython.h.  Then copy it to
> /usr/include/wx/wxPython/wxPython.h.   I will attach mine, but this
> may be a bad idea.  You can download from their webpage here:
> http://www.wxpython.org/download.php#sources
> (grab the first one in the list that doesn't say RPM - it is the tar.gz file).

You will also need to install the wxWidgets "-dev" package, since that's where 
the "wx-config" program lives.

Ken

You might get all the development packages you will ever need in one
step if you install gnome-devel  - but it is a huge package with a lot
of dependencies that could take a while to install.   But it might
keep you from hunting for individual packages needed by mpl backends.

Ryan

On 10/27/05, Ryan Krauss <rya...@gm...> wrote:
> You will also need the packages tk8.4 and tk8.4-dev for the Tk backend
> (your version numbers might be slightly less if you are on Hoary).
>
> Ryan
>
> On 10/27/05, Christian Meesters <mee...@un...> wrote:
> > Hi Ryan,
> >
> > Thanks, but I too run into problems:
> > Doing python setup.py build is fine until:
> > <snip>
> > src/_na_backend_gdk.c:12:25: error: pygtk/pygtk.h: No such file or
> > directory
> > src/_na_backend_gdk.c: In function 'pixbuf_get_pixels_array':
> > src/_na_backend_gdk.c:31: error: 'PyGObject' undeclared (first use in
> > this function)
> > src/_na_backend_gdk.c:31: error: (Each undeclared identifier is reporte=
d
> > only once
> > src/_na_backend_gdk.c:31: error: for each function it appears in.)
> > src/_na_backend_gdk.c:31: error: 'py_pixbuf' undeclared (first use in
> > this function)
> > src/_na_backend_gdk.c:32: error: 'GdkPixbuf' undeclared (first use in
> > this function)
> > src/_na_backend_gdk.c:32: error: 'gdk_pixbuf' undeclared (first use in
> > this function)
> > src/_na_backend_gdk.c:40: warning: implicit declaration of function
> > 'GDK_PIXBUF'
> > src/_na_backend_gdk.c:46: warning: implicit declaration of function
> > 'gdk_pixbuf_get_height'
> > src/_na_backend_gdk.c:47: warning: implicit declaration of function
> > 'gdk_pixbuf_get_width'
> > src/_na_backend_gdk.c:48: warning: implicit declaration of function
> > 'gdk_pixbuf_get_has_alpha'
> > src/_na_backend_gdk.c:52: warning: implicit declaration of function
> > 'gdk_pixbuf_get_pixels'
> > src/_na_backend_gdk.c:52: warning: cast to pointer from integer of
> > different size
> > src/_na_backend_gdk.c:56: warning: implicit declaration of function
> > 'gdk_pixbuf_get_rowstride'
> > src/_na_backend_gdk.c: In function 'init_na_backend_gdk':
> > src/_na_backend_gdk.c:84: warning: implicit declaration of function
> > 'init_pygtk'
> > error: command 'gcc' failed with exit status 1
> >
> > Apparently the autodetection fails. Then I disabled all backends (excep=
t
> > for Agg, WX, WXAgg, which I want to use) and next time I tried setup.py
> > build:
> >
> > WXAgg's accelerator requires `wx-config'.
> >
> > The `wx-config' executable could not be located in any directory of the
> > PATH
> > environment variable.  If it is in some other location or has some othe=
r
> > name,
> > set the WX_CONFIG environment variable to the full path of the
> > executable.
> >
> > Sounds familiar, doesn't it? ;-)
> >
> > Now, I tried to read on and in the end I am - frankly - completely
> > confused. Since I can't compile (I tried some other tweaks) ... is
> > somebody able to compile installation instructions? It appears that the
> > part on matplotlib's web page isn't up to date (how to build, the issue
> > with the debian's package, possibly other problems yet not seen by me?)=
.
> > I would be willing to test everything shown to me and summarize this.
> > (Alas, I don't know how to build packages myself yet and I fear I won't
> > have the time to do anything quickly.)
> >
> > Cheers,
> > Christian
> >
> >
> >
> >
>

You will also need the packages tk8.4 and tk8.4-dev for the Tk backend
(your version numbers might be slightly less if you are on Hoary).

Ryan

On 10/27/05, Christian Meesters <mee...@un...> wrote:
> Hi Ryan,
>
> Thanks, but I too run into problems:
> Doing python setup.py build is fine until:
> <snip>
> src/_na_backend_gdk.c:12:25: error: pygtk/pygtk.h: No such file or
> directory
> src/_na_backend_gdk.c: In function 'pixbuf_get_pixels_array':
> src/_na_backend_gdk.c:31: error: 'PyGObject' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:31: error: (Each undeclared identifier is reported
> only once
> src/_na_backend_gdk.c:31: error: for each function it appears in.)
> src/_na_backend_gdk.c:31: error: 'py_pixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:32: error: 'GdkPixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:32: error: 'gdk_pixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:40: warning: implicit declaration of function
> 'GDK_PIXBUF'
> src/_na_backend_gdk.c:46: warning: implicit declaration of function
> 'gdk_pixbuf_get_height'
> src/_na_backend_gdk.c:47: warning: implicit declaration of function
> 'gdk_pixbuf_get_width'
> src/_na_backend_gdk.c:48: warning: implicit declaration of function
> 'gdk_pixbuf_get_has_alpha'
> src/_na_backend_gdk.c:52: warning: implicit declaration of function
> 'gdk_pixbuf_get_pixels'
> src/_na_backend_gdk.c:52: warning: cast to pointer from integer of
> different size
> src/_na_backend_gdk.c:56: warning: implicit declaration of function
> 'gdk_pixbuf_get_rowstride'
> src/_na_backend_gdk.c: In function 'init_na_backend_gdk':
> src/_na_backend_gdk.c:84: warning: implicit declaration of function
> 'init_pygtk'
> error: command 'gcc' failed with exit status 1
>
> Apparently the autodetection fails. Then I disabled all backends (except
> for Agg, WX, WXAgg, which I want to use) and next time I tried setup.py
> build:
>
> WXAgg's accelerator requires `wx-config'.
>
> The `wx-config' executable could not be located in any directory of the
> PATH
> environment variable.  If it is in some other location or has some other
> name,
> set the WX_CONFIG environment variable to the full path of the
> executable.
>
> Sounds familiar, doesn't it? ;-)
>
> Now, I tried to read on and in the end I am - frankly - completely
> confused. Since I can't compile (I tried some other tweaks) ... is
> somebody able to compile installation instructions? It appears that the
> part on matplotlib's web page isn't up to date (how to build, the issue
> with the debian's package, possibly other problems yet not seen by me?).
> I would be willing to test everything shown to me and summarize this.
> (Alas, I don't know how to build packages myself yet and I fear I won't
> have the time to do anything quickly.)
>
> Cheers,
> Christian
>
>
>
>

Do you have the package "python-gtk2-dev" installed?  You will need
this for the pygtk headers.  Wx is a pain at the moment, but if you
are happy with gtk you should have no problems on ubuntu.

On 10/27/05, Christian Meesters <mee...@un...> wrote:
> Hi Ryan,
>
> Thanks, but I too run into problems:
> Doing python setup.py build is fine until:
> <snip>
> src/_na_backend_gdk.c:12:25: error: pygtk/pygtk.h: No such file or
> directory
> src/_na_backend_gdk.c: In function 'pixbuf_get_pixels_array':
> src/_na_backend_gdk.c:31: error: 'PyGObject' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:31: error: (Each undeclared identifier is reported
> only once
> src/_na_backend_gdk.c:31: error: for each function it appears in.)
> src/_na_backend_gdk.c:31: error: 'py_pixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:32: error: 'GdkPixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:32: error: 'gdk_pixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:40: warning: implicit declaration of function
> 'GDK_PIXBUF'
> src/_na_backend_gdk.c:46: warning: implicit declaration of function
> 'gdk_pixbuf_get_height'
> src/_na_backend_gdk.c:47: warning: implicit declaration of function
> 'gdk_pixbuf_get_width'
> src/_na_backend_gdk.c:48: warning: implicit declaration of function
> 'gdk_pixbuf_get_has_alpha'
> src/_na_backend_gdk.c:52: warning: implicit declaration of function
> 'gdk_pixbuf_get_pixels'
> src/_na_backend_gdk.c:52: warning: cast to pointer from integer of
> different size
> src/_na_backend_gdk.c:56: warning: implicit declaration of function
> 'gdk_pixbuf_get_rowstride'
> src/_na_backend_gdk.c: In function 'init_na_backend_gdk':
> src/_na_backend_gdk.c:84: warning: implicit declaration of function
> 'init_pygtk'
> error: command 'gcc' failed with exit status 1
>
> Apparently the autodetection fails. Then I disabled all backends (except
> for Agg, WX, WXAgg, which I want to use) and next time I tried setup.py
> build:
>
> WXAgg's accelerator requires `wx-config'.
>
> The `wx-config' executable could not be located in any directory of the
> PATH
> environment variable.  If it is in some other location or has some other
> name,
> set the WX_CONFIG environment variable to the full path of the
> executable.
>
> Sounds familiar, doesn't it? ;-)
>
> Now, I tried to read on and in the end I am - frankly - completely
> confused. Since I can't compile (I tried some other tweaks) ... is
> somebody able to compile installation instructions? It appears that the
> part on matplotlib's web page isn't up to date (how to build, the issue
> with the debian's package, possibly other problems yet not seen by me?).
> I would be willing to test everything shown to me and summarize this.
> (Alas, I don't know how to build packages myself yet and I fear I won't
> have the time to do anything quickly.)
>
> Cheers,
> Christian
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

I know this can be frustrating, but hang in there.

Your initial error about pygtk.h not being found is a dependency
error.  You need some other packages and I am not sure what they all
are. They are generally the development packages.  For this one,
search in the Synaptics package manager for pygtk and find
python-gtk2-dev (and probably python-gnome2-dev).  You may run into a
few more of these.  Whenever you see a *.h: No such file error, you
have a dev package missing.

The only way around the wx-config error is to download the wxPython
source tarball and find wxPython.h.  Then copy it to
/usr/include/wx/wxPython/wxPython.h.   I will attach mine, but this
may be a bad idea.  You can download from their webpage here:
http://www.wxpython.org/download.php#sources
(grab the first one in the list that doesn't say RPM - it is the tar.gz fil=
e).

So, copying wxPython.h from the tarball or the attached file should
solve the wx-config error (you may need the other *.h files in the
same folder of the tarball). Working through the dev packages should
solve the errors with the other backends.  I have TkAgg, GTKAgg,
WXAgg, and PS working on mine (there are probably others, but those I
have tested).

Let me know if you need more info.

Ryan


On 10/27/05, Christian Meesters <mee...@un...> wrote:
> Hi Ryan,
>
> Thanks, but I too run into problems:
> Doing python setup.py build is fine until:
> <snip>
> src/_na_backend_gdk.c:12:25: error: pygtk/pygtk.h: No such file or
> directory
> src/_na_backend_gdk.c: In function 'pixbuf_get_pixels_array':
> src/_na_backend_gdk.c:31: error: 'PyGObject' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:31: error: (Each undeclared identifier is reported
> only once
> src/_na_backend_gdk.c:31: error: for each function it appears in.)
> src/_na_backend_gdk.c:31: error: 'py_pixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:32: error: 'GdkPixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:32: error: 'gdk_pixbuf' undeclared (first use in
> this function)
> src/_na_backend_gdk.c:40: warning: implicit declaration of function
> 'GDK_PIXBUF'
> src/_na_backend_gdk.c:46: warning: implicit declaration of function
> 'gdk_pixbuf_get_height'
> src/_na_backend_gdk.c:47: warning: implicit declaration of function
> 'gdk_pixbuf_get_width'
> src/_na_backend_gdk.c:48: warning: implicit declaration of function
> 'gdk_pixbuf_get_has_alpha'
> src/_na_backend_gdk.c:52: warning: implicit declaration of function
> 'gdk_pixbuf_get_pixels'
> src/_na_backend_gdk.c:52: warning: cast to pointer from integer of
> different size
> src/_na_backend_gdk.c:56: warning: implicit declaration of function
> 'gdk_pixbuf_get_rowstride'
> src/_na_backend_gdk.c: In function 'init_na_backend_gdk':
> src/_na_backend_gdk.c:84: warning: implicit declaration of function
> 'init_pygtk'
> error: command 'gcc' failed with exit status 1
>
> Apparently the autodetection fails. Then I disabled all backends (except
> for Agg, WX, WXAgg, which I want to use) and next time I tried setup.py
> build:
>
> WXAgg's accelerator requires `wx-config'.
>
> The `wx-config' executable could not be located in any directory of the
> PATH
> environment variable.  If it is in some other location or has some other
> name,
> set the WX_CONFIG environment variable to the full path of the
> executable.
>
> Sounds familiar, doesn't it? ;-)
>
> Now, I tried to read on and in the end I am - frankly - completely
> confused. Since I can't compile (I tried some other tweaks) ... is
> somebody able to compile installation instructions? It appears that the
> part on matplotlib's web page isn't up to date (how to build, the issue
> with the debian's package, possibly other problems yet not seen by me?).
> I would be willing to test everything shown to me and summarize this.
> (Alas, I don't know how to build packages myself yet and I fear I won't
> have the time to do anything quickly.)
>
> Cheers,
> Christian
>
>
>
>

Hi Ryan,

Thanks, but I too run into problems:
Doing python setup.py build is fine until:
<snip>
src/_na_backend_gdk.c:12:25: error: pygtk/pygtk.h: No such file or
directory
src/_na_backend_gdk.c: In function =E2=80=98pixbuf_get_pixels_array=E2=80=
=99:
src/_na_backend_gdk.c:31: error: =E2=80=98PyGObject=E2=80=99 undeclared (=
first use in
this function)
src/_na_backend_gdk.c:31: error: (Each undeclared identifier is reported
only once
src/_na_backend_gdk.c:31: error: for each function it appears in.)
src/_na_backend_gdk.c:31: error: =E2=80=98py_pixbuf=E2=80=99 undeclared (=
first use in
this function)
src/_na_backend_gdk.c:32: error: =E2=80=98GdkPixbuf=E2=80=99 undeclared (=
first use in
this function)
src/_na_backend_gdk.c:32: error: =E2=80=98gdk_pixbuf=E2=80=99 undeclared =
(first use in
this function)
src/_na_backend_gdk.c:40: warning: implicit declaration of function
=E2=80=98GDK_PIXBUF=E2=80=99
src/_na_backend_gdk.c:46: warning: implicit declaration of function
=E2=80=98gdk_pixbuf_get_height=E2=80=99
src/_na_backend_gdk.c:47: warning: implicit declaration of function
=E2=80=98gdk_pixbuf_get_width=E2=80=99
src/_na_backend_gdk.c:48: warning: implicit declaration of function
=E2=80=98gdk_pixbuf_get_has_alpha=E2=80=99
src/_na_backend_gdk.c:52: warning: implicit declaration of function
=E2=80=98gdk_pixbuf_get_pixels=E2=80=99
src/_na_backend_gdk.c:52: warning: cast to pointer from integer of
different size
src/_na_backend_gdk.c:56: warning: implicit declaration of function
=E2=80=98gdk_pixbuf_get_rowstride=E2=80=99
src/_na_backend_gdk.c: In function =E2=80=98init_na_backend_gdk=E2=80=99:
src/_na_backend_gdk.c:84: warning: implicit declaration of function
=E2=80=98init_pygtk=E2=80=99
error: command 'gcc' failed with exit status 1

Apparently the autodetection fails. Then I disabled all backends (except
for Agg, WX, WXAgg, which I want to use) and next time I tried setup.py
build:

WXAgg's accelerator requires `wx-config'.

The `wx-config' executable could not be located in any directory of the
PATH
environment variable.  If it is in some other location or has some other
name,
set the WX_CONFIG environment variable to the full path of the
executable.

Sounds familiar, doesn't it? ;-)

Now, I tried to read on and in the end I am - frankly - completely
confused. Since I can't compile (I tried some other tweaks) ... is
somebody able to compile installation instructions? It appears that the
part on matplotlib's web page isn't up to date (how to build, the issue
with the debian's package, possibly other problems yet not seen by me?).
I would be willing to test everything shown to me and summarize this.
(Alas, I don't know how to build packages myself yet and I fear I won't
have the time to do anything quickly.)

Cheers,
Christian

Following Darren's advice, I downloaded and built from source gs-gpl
8.15 (not yet available in the ubuntu package manager) and this
problem went away.

Thanks Darren.

Ryan

On 10/27/05, Darren Dale <dd...@co...> wrote:
> On Thursday 27 October 2005 11:42 am, you wrote:
> > I don't think I have anything funny in my matplotlibrc file, but it is
> > attached just in case.  (It includes a recent patch I made to make the
> > legend customizable from the RC file, so you may need to comment that
> > out if you actually try to use my RC file.)
> >
> > Let me know if you want me to try anything else.  8.14 is the latest
> > version released through the ubuntu package manager.
>
> My first guess is that it is a problem with your ghostscript. Can you ins=
tall
> ghostscript-gnu-8.16?
>
> I am currently on vacation, starting a new job on Tuesday. So I will prob=
ably
> not be at the computer much during the next week. I hope a change in
> ghostscript helps.
>
> Darren
>

Sorry, I meant version 8.16.

On 10/27/05, Ryan Krauss <rya...@gm...> wrote:
> Following Darren's advice, I downloaded and built from source gs-gpl
> 8.15 (not yet available in the ubuntu package manager) and this
> problem went away.
>
> Thanks Darren.
>
> Ryan
>
> On 10/27/05, Darren Dale <dd...@co...> wrote:
> > On Thursday 27 October 2005 11:42 am, you wrote:
> > > I don't think I have anything funny in my matplotlibrc file, but it i=
s
> > > attached just in case.  (It includes a recent patch I made to make th=
e
> > > legend customizable from the RC file, so you may need to comment that
> > > out if you actually try to use my RC file.)
> > >
> > > Let me know if you want me to try anything else.  8.14 is the latest
> > > version released through the ubuntu package manager.
> >
> > My first guess is that it is a problem with your ghostscript. Can you i=
nstall
> > ghostscript-gnu-8.16?
> >
> > I am currently on vacation, starting a new job on Tuesday. So I will pr=
obably
> > not be at the computer much during the next week. I hope a change in
> > ghostscript helps.
> >
> > Darren
> >
>

Darren,

Thanks for your willingness to help.  A small script is attached and
the figure it produces is attached as well.  When I view the eps with
gv and set it to show the bounding box, it clips tightly around the
figure without the axis labels or tick marks.  I ran the figure
through epstopdf and it uses the same bounding box produces the same
figure minus axis and tick mark labels.

I don't think I have anything funny in my matplotlibrc file, but it is
attached just in case.  (It includes a recent patch I made to make the
legend customizable from the RC file, so you may need to comment that
out if you actually try to use my RC file.)

Let me know if you want me to try anything else.  8.14 is the latest
version released through the ubuntu package manager.

Ryan

On 10/26/05, Darren Dale <dd...@co...> wrote:
> On Tuesday 25 October 2005 11:46 pm, Ryan Krauss wrote:
> > ryan@ubuntu:~/datafit/closed_loop_modeling_report/figs$ gs -v
> > AFPL Ghostscript 8.14 (2004-02-20)
> > Copyright (C) 2004 artofcode LLC, Benicia, CA.  All rights reserved.
> >
> > The bounding box goes tightly around the figure but does not include
> > the labels.  Is there a way to add a pad around the figure or some
> > other way to solve this problem?
>
> I haven't seen this problem before, would you post a minimal example?
>
> Darren
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hey Ken,

Sorry to make more work for you.  Yes, turning off the accelerator
gets rid of the seg fault:
In [7]: %hist
1:  import matplotlib.backends.backend_wxagg
2: import matplotlib.backends.backend_wxagg
3: matplotlib.backends.backend_wxagg._use_accelerator(False)
4: matplotlib.__version__
5: figure(1)
6: show()
>>>after this show command an empty plot pops up with problem.  Then
reactivating the accelerator leads to the seg fault:

In [8]: matplotlib.backends.backend_wxagg._use_accelerator(True)

In [9]: pylab.close('all')

In [10]: figure(1)
Segmentation fault

Let me know what to try next.  Another strace?

Ryan

On 10/26/05, Ken McIvor <mc...@ii...> wrote:
> Ryan,
>
> Could you please test and see if the segfaults continue to occur when the
> WxAgg accelerator has been disabled?  Also, short script that reproduces =
this
> problem would be appreciated.  Thanks.
>
> Ken
>

I recently installed matplotlib on ubuntu Breezy and it went fairly
well.  I was having some problems that I thought were from John's
package not working on Breezy but turned out to be something else.  I
ended up installing from source.  It is fairly straight forward to
download the tarball and do a sudo python setup.py install.  I ran
into some problems with needing the wxPython.h header file for the
WXAgg backend.  If you look for a thread I started with the subject
"WXAgg's accelerator requires `wx-config'." you should find that Ken
and Arnd got me through it.  Let me know if you get stuck anywhere.

Ryan

On 10/27/05, Christian Meesters <mee...@un...> wrote:
> Hi all, Hi John,
>
> I remembered that there was a recent post on installing matplotlib on
> Ubuntu.
>
> I tried apt-get update without an error message, but running apt-get
> install python-matplotlib-jdh gives me the following output.
>
> Reading package lists... Done
> Building dependency tree... Done
> Package python-matplotlib-jdh is not available, but is referred to by
> another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> E: Package python-matplotlib-jdh has no installation candidate
>
> Apparently something changed since your post and now John. Is the
> package still available? What else would be a convenient way to install?
>
> Well, I fear my question will turn out to be stupid, but I really have
> no idea where to look for my mistake anymore.
>
> TIA
> Christian
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hi all, Hi John,

I remembered that there was a recent post on installing matplotlib on
Ubuntu.

I tried apt-get update without an error message, but running apt-get
install python-matplotlib-jdh gives me the following output.

Reading package lists... Done
Building dependency tree... Done
Package python-matplotlib-jdh is not available, but is referred to by
another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package python-matplotlib-jdh has no installation candidate

Apparently something changed since your post and now John. Is the
package still available? What else would be a convenient way to install?

Well, I fear my question will turn out to be stupid, but I really have
no idea where to look for my mistake anymore.

TIA
Christian

On Thursday 27 October 2005 8:38 am, Nils Wagner wrote:
> Hi all,
>
> Is it possible to use \mathds{R} in pylab ?
>
> In LaTeX this becomes available through
> \usepackage{dsfont}

just set the following in your matplotlibrc:

font.latex.package  : dsfont

Hi all,

Is it possible to use \mathds{R} in pylab ?

In LaTeX this becomes available through
\usepackage{dsfont}

Nils

Hi,
I've recently started using pylab, and its not clear to me how to do a 2d 
animation.

If I have a 3d numeric array (eg 
arr=RandomArray.randint(0,127,(100,256,256)))
how can I display arr[0], then arr[1], then...

The way I've tried seems to slow down as I progress, suggesting that its 
drawing all previous arrays before drawing the current one.

Thanks...

> Looks like a bug -- I see the same thing with twinx.  Could you file
> this one of the sf site?   I took a look through the axis code but
> couldn't find the culprit.  I'm CC Baptiste who wrote the code --
> maybe he has some insight.
>
It is indeed a bug. Imho we should fix it in pylab.py, by changing the
function twinx to read:

def twinx(ax=3DNone):
    """
    Make a second axes overlay ax (or the current axes if ax is None)
    sharing the xaxis.  The ticks for ax2 will be placed on the right,
    and the ax2 instance is returned.  See examples/two_scales.py
    """
    if ax is None:
        ax=3Dgca()


    ax2 =3D gcf().add_axes(ax.get_position(), sharex=3Dax, frameon=3DFals=
e)
    ax2.yaxis.tick_right()
    ax2.yaxis.set_label_position('right')

    ax.yaxis.tick_left()

    draw_if_interactive()
    return ax2

The attached one-line patch does the trick.

Cheers, Baptiste

Dear John,

JDH> -----Original Message-----
JDH> From: John Hunter [mailto:jdh...@ac...]=20

JDH> I don't think you need both.  I think you could just do
JDH>=20
JDH>     rcParams['font.latex.filename'] =3D 'mypresentation.llfc'
JDH>     rcParams['font.latex.filename'] =3D  None

Good idea... nice and clean...

JDH>     PJ> The "low level font command" input file has the
JDH>     PJ> following included:
JDH>=20
JDH> I think it would be much easier for us to deal with this=20
JDH> if you submit it as a proper patch against CVS and upload=20
JDH> it to the sf site.

I'm not following... This "low level font command" input file is user
specific...

JDH>     PJ> ...  def get_tex_command(self, tex, fname): fh =3D
JDH>     PJ> file(fname, 'w') if rcParams['text.tex.engine'] =3D=3D
JDH>     PJ> 'latex': print >>fh, r"""\documentclass{article}
JDH>     PJ> \usepackage{%s} \setlength{\paperwidth}{72in}
JDH>     PJ> \setlength{\paperheight}{72in} \pagestyle{empty}
JDH>     PJ> \begin{document}""" % (rcParams['font.latex.package'])
JDH>     PJ> if rcParams['font.latex.inputfile']: inputfile =3D
JDH>     PJ> rcParams['font.latex.inputfile.filename'] if
JDH>     PJ> os.path.exists(inputfile): print >>fh, r"\input{%s}" %
JDH>     PJ> inputfile print >>fh, r"""%s \end{document}""" % tex
JDH>=20
JDH> I worry that this is starting to get hairy -- perhaps we=20
JDH> should look into separating the latex from the code more cleanly.

I think the problem here has to do with Windows line breaks on non
Windows computers...

Was the attached file just as "hairy"...?

JDH> I think it would be much easier for us to deal with this=20
JDH> if you submit it as a proper patch against CVS and upload=20
JDH> it to the sf site. Could I trouble you to do that?

Yes, but first I would like to add a some python code to allow for a
"LaTeX preamble" input file for stuff like:

\DeclareMathAlphabet\mathscr{T1}{futs}{m}{it}

For custom mathscript or for custom macro definitions used within mpl
text..


User would also be able to load additional packages, like:

\usepackage[afrikaans,english]{babel} % Or other languages
\usepackage[iso,english]{isodate}     % For ISO style date format in
conjunction with the babel package
\usepackage{numprint}                 % For 123 456,789 number format
instead of 123,456.789


There would then be two optional LaTeX input files:

- a "LaTeX preamble" input file and/or
- a "low level font command" input file

(it would be difficult to combine them into one...)

Selectable with:

rcParams[latex.preamble.filename'] =3D 'MySimmulation.prbl
rcParams[latex.lowlevelfontcommand.filename] =3D 'MyPresentation.llfc'

Any suggestions for better rcParams names... (and extension... or is it
necessary, it could actually be anything... but a standard would be...
"nice")

Finally, with:

\usepackage{helvet}

in the "LaTeX preamble" input file,=20

rcParams['font.latex.package'] would become unnecessary... but IMHO
should be retained...


Kind regards,

   Peter-Jan Randewijk
   Senior Lektor - Drywingselektronika & Elektriese Aandrywing =20
=20
-oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOo-=20
    Departement E&E. Ingenieurswese
    Universiteit Stellenbosch=20
    Privaatsak X1=20
    Matieland, 7603
    Suid-Afrika
    Tel:  +27 (0) 21 808 4457 (w)=20
    Faks: +27 (0) 21 808 3951 (w)=20
    Tel:  +27 (0) 21 883 8592 (h)=20
    Sel:  +27 (0) 83 556 5809 (h)
-oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOo-=20

>>>>> ""Randewijk" == "Randewijk P-J <pjr...@su...>" <pjr...@su...> writes:

    PJ> Dear All, I have hacked a bit at texmanager.py and
    PJ> backend_ps.py in order to generate "superior" text
    PJ> output using LaTeX.

Thanks for the changes!

    PJ> It involves "including" a user specific "low level
    PJ> font command" input file useing some "new" rcParams
    PJ> and the savefig command with the PS backend in you
    PJ> main "pylab" script:

    PJ> ...  rcParams['font.latex.inputfile']='True'
    PJ> rcParams['font.latex.inputfile.filename']='mypresentation.llfc'

I don't think you need both.  I think you could just do

    rcParams['font.latex.filename'] = 'mypresentation.llfc'
    rcParams['font.latex.filename'] =  None

    PJ> savefig('myeps.eps') ...


    PJ> The "low level font command" input file has the
    PJ> following included:

I think it would be much easier for us to deal with this if you submit
it as a proper patch against CVS and upload it to the sf site.  Could
I trouble you to do that?

    PJ> ...  def get_tex_command(self, tex, fname): fh =
    PJ> file(fname, 'w') if rcParams['text.tex.engine'] ==
    PJ> 'latex': print >>fh, r"""\documentclass{article}
    PJ> \usepackage{%s} \setlength{\paperwidth}{72in}
    PJ> \setlength{\paperheight}{72in} \pagestyle{empty}
    PJ> \begin{document}""" % (rcParams['font.latex.package'])
    PJ> if rcParams['font.latex.inputfile']: inputfile =
    PJ> rcParams['font.latex.inputfile.filename'] if
    PJ> os.path.exists(inputfile): print >>fh, r"\input{%s}" %
    PJ> inputfile print >>fh, r"""%s \end{document}""" % tex

I worry that this is starting to get hairy -- perhaps we should look
into separating the latex from the code more cleanly.

JDH