SourceForge logo
SourceForge logo
Menu

matplotlib-users — Discussion related to using matplotlib

You can subscribe to this list here.

2003 Jan
Feb
Mar
Apr
May
(3)
Jun
Jul
Aug
(12)
Sep
(12)
Oct
(56)
Nov
(65)
Dec
(37)
2004 Jan
(59)
Feb
(78)
Mar
(153)
Apr
(205)
May
(184)
Jun
(123)
Jul
(171)
Aug
(156)
Sep
(190)
Oct
(120)
Nov
(154)
Dec
(223)
2005 Jan
(184)
Feb
(267)
Mar
(214)
Apr
(286)
May
(320)
Jun
(299)
Jul
(348)
Aug
(283)
Sep
(355)
Oct
(293)
Nov
(232)
Dec
(203)
2006 Jan
(352)
Feb
(358)
Mar
(403)
Apr
(313)
May
(165)
Jun
(281)
Jul
(316)
Aug
(228)
Sep
(279)
Oct
(243)
Nov
(315)
Dec
(345)
2007 Jan
(260)
Feb
(323)
Mar
(340)
Apr
(319)
May
(290)
Jun
(296)
Jul
(221)
Aug
(292)
Sep
(242)
Oct
(248)
Nov
(242)
Dec
(332)
2008 Jan
(312)
Feb
(359)
Mar
(454)
Apr
(287)
May
(340)
Jun
(450)
Jul
(403)
Aug
(324)
Sep
(349)
Oct
(385)
Nov
(363)
Dec
(437)
2009 Jan
(500)
Feb
(301)
Mar
(409)
Apr
(486)
May
(545)
Jun
(391)
Jul
(518)
Aug
(497)
Sep
(492)
Oct
(429)
Nov
(357)
Dec
(310)
2010 Jan
(371)
Feb
(657)
Mar
(519)
Apr
(432)
May
(312)
Jun
(416)
Jul
(477)
Aug
(386)
Sep
(419)
Oct
(435)
Nov
(320)
Dec
(202)
2011 Jan
(321)
Feb
(413)
Mar
(299)
Apr
(215)
May
(284)
Jun
(203)
Jul
(207)
Aug
(314)
Sep
(321)
Oct
(259)
Nov
(347)
Dec
(209)
2012 Jan
(322)
Feb
(414)
Mar
(377)
Apr
(179)
May
(173)
Jun
(234)
Jul
(295)
Aug
(239)
Sep
(276)
Oct
(355)
Nov
(144)
Dec
(108)
2013 Jan
(170)
Feb
(89)
Mar
(204)
Apr
(133)
May
(142)
Jun
(89)
Jul
(160)
Aug
(180)
Sep
(69)
Oct
(136)
Nov
(83)
Dec
(32)
2014 Jan
(71)
Feb
(90)
Mar
(161)
Apr
(117)
May
(78)
Jun
(94)
Jul
(60)
Aug
(83)
Sep
(102)
Oct
(132)
Nov
(154)
Dec
(96)
2015 Jan
(45)
Feb
(138)
Mar
(176)
Apr
(132)
May
(119)
Jun
(124)
Jul
(77)
Aug
(31)
Sep
(34)
Oct
(22)
Nov
(23)
Dec
(9)
2016 Jan
(26)
Feb
(17)
Mar
(10)
Apr
(8)
May
(4)
Jun
(8)
Jul
(6)
Aug
(5)
Sep
(9)
Oct
(4)
Nov
Dec
2017 Jan
(5)
Feb
(7)
Mar
(1)
Apr
(5)
May
Jun
(3)
Jul
(6)
Aug
(1)
Sep
Oct
(2)
Nov
(1)
Dec
2018 Jan
Feb
Mar
Apr
(1)
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
2020 Jan
Feb
Mar
Apr
May
(1)
Jun
Jul
Aug
Sep
Oct
Nov
Dec
2025 Jan
(1)
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
S M T W T F S



1
(14)
2
(31)
3
(20)
4
(4)
5
(2)
6
(10)
7
(25)
8
(13)
9
(3)
10
(5)
11
(2)
12
(1)
13
(19)
14
(16)
15
(18)
16
(7)
17
(17)
18
19
(2)
20
(7)
21
(12)
22
(14)
23
(8)
24
(6)
25
(3)
26
27
(21)
28
(8)
29
(5)
30
(6)


Showing 13 results of 13

From: Chris B. <Chr...@no...> - 2005年06月08日 22:38:48
Charles Moad wrote:
> Installing each
> dependency would probably be just as easy as trying to use components
> from my installer.
I put instructions for how to do this in my package for OS-X-10.3,
py2.3.0. Here they are. If you do all this, you can donate the package
to Bob's repository on pythonmac.org.
There is a related thread about defining a standard way to do this for
matplotlib, so it will build out of the box.
They should work just fine for newer versions of OS, matplotlib, and
python. Sorry they are a bit wordy:
Installing matplotlib on OS-X (10.3.7)
Here are my notes as to what it took to get matplotlib (0.71) installed
and working on OS-X. I have so far kept a fink-free system, so that's
what I've done here as well. I use it with the AGG back end for
generating images for a web site, and hopefully with the wx backend for
interactive use and embedding in wx Applications. I've also quickly got
it working with TK. Note that this is kind of a running commentary, not
well edited. I'd read the whole thing before starting.
1) Requirements:
-------------------------------------------
According to the matplotlib install docs
(http://matplotlib.sourceforge.net/installing.html), you need the following:
freetype (>= 2.1.7)
libpng
zlib
Personally, I've been avoiding Fink, as it doesn't seem to play well
with the rest of OS-X, including the Apple supplied Python, so I've
looked elsewhere for these libs.
a) Freetype:
I seem to have it in:
/usr/X11R6/include/freetype2
I don't think I installed it myself, so it probably came with Apple's
X11, Which I did install.
However, I seemed to be having problems with that version, so I looked,
and it seems to be:
libfreetype.6.3.dylib
Given that freetype2 is currently at version 2.1.9, I have no idea what
to make of that! So off to sourceforge to get a new freetype:
http://freetype.sourceforge.net/index2.html
where I got:
freetype-2.1.9.tar.gz
Following the instructions in docs/INSTALL.UNX:
$ ./configure
$ make
$ sudo make install
That puts it in /usr/local/..., which is a good place for it.
NOTE: The above will build freetype as a shared library, which is fine
if you are building ot run on the same system you are building on.
However, if you want to buuild a re-distributable package, you'll need a
static library, which you can get by doing:
$ ./configure --disable-shared --enable static
$ make
$ sudo make install
Hmm. that made the static libs (*.a) , but also the dynamic ones.
Make sure to do:
$ make clean
if you had already built it. You may also have to remove the shared
libs, so that they won't be found (*.dyld). I had to remove them from
/usr/local/lib.
b) zlib:
I have:
/usr/include/zlib.h
I don't know where I might have gotten it, but there it is.
NOTE: I checked on another system in my office, and it doesn't have
zlib. It does, however have libz, which I am told is the same thing, to
you shouldn't need this.
c) libpng:
This, I didn't have on my system, except inside the wxWidgets source
tree, so I went looking for it.
Note that you need zlib to compile libpng, so make sure you have that first.
I did a google search for "libpng OS-X". I found:
http://www.libpng.org/pub/png/pngcode.html
Which led me to the libpng sourceforge site.
 From there I downloaded:
libpng-1.2.8.tar.gz
unpacked it, and opened a terminal in the libpng-1.2.8 directory, and did:
$ cp scripts/makefile.darwin ./makefile
(note that according to the INSTALL, there is supposed to be a
makefile.macosx, but it wasn't there)
I took a look in the makefile, and found:
ZLIBLIB=/usr/local/lib
ZLIBINC=/usr/local/include
Which is not where zlib is on my system. However, while I can find
zlib.h, I couldn't fine the actual lib, so I tried make without changing
anything.
$ make
Which seemed to work fine. zlib must be installed in a standard
location, and gcc found it.
$ sudo make install
to install the lib into /usr/local/ (this was specified in the makefile,
and it's a good place for it)
$ make test
and
$ ./pngtest pngnow.png
Which both seemed to pass.
If you want to build a re-distributable version of matplotlib, you need
the static version of libpng, instead of the dynamic one. It doesn't use
./configure, so instead, I did a:
sudo make install-static
and that installed the *.a files in /usr/local/lib.
d) Numeric or numarray:
I already have Numeric installed, from Bob Ippolito's PIMP (MacPython
Package Manager) repostitory. (www.undefined.org/python)
2) Building matplotlib
---------------------------------------------------------
First, I took a look at the matplotlib setup.py. It had "auto" for the
back-end flags, so I thought I would give it a try that way:
$python setup.py build
If you have only the static version of libpng and libfreetype (*.a, and
not *.dylib) in /usr/local/lib (or anywhere else on your lib search
path), then it should link those statically.
That worked!
$ sudo python setup.py install
4) And now to test!
$python
>>> import pylab
Could not open font file /Library/Fonts/NISC18030.ttf
No module named pygtk
PyGTK version 1.99.16 or greater is required to run the GTK Matplotlib
backends
This turns out to be because the matlabrc file sets the GTKAgg back end
as the default. You have two choices.
1) you can set the back end before importing pylab.
>>> import matplotlib
>>> matplotlib.use('Agg')
>>> import pylab
This works fine
2) Edit the matplotlibrc file. I found it in:
/System/Library/Frameworks/Python.framework/Versions/2.3/share/matplotlib/.matplotlibrc
Change the line:
backend : GTKAgg # the default backend
to
backend : Agg # the default backend
And you're all set to make images for the web, etc.
I'm going to leave getting it to work with wxPython for another day.
3) Building a matplotlib Binary Package for OS-X:
First you need to make sure you've got libpng and libfreetype staticaly
linked. I did this by copying the headers and *.a files for them into a
directory I created called "StaticLibs", in the main matplot lib
directory (the one setup,py is in). You could just as easily put in
links, rather than copies, probably a better idea, actually.
Then I edited setupext.py, so that distutils would only look there:
basedir = {
 'win32' : ['win32_static',],
 'linux2' : ['/usr/local', '/usr',],
 'linux' : ['/usr/local', '/usr',],
# 'darwin' : ['/usr/local', '/usr', '/sw', '/usr/X11R6'],
 'darwin' : ['StaticLibs'],
 'freebsd4' : ['/usr/local', '/usr'],
 'sunos5' : [os.getenv('MPLIB_BASE') or '/usr/local',],
}
I'm talking to John Hunter about having a conditional Static setup in
the official setup.py to support this. This seemed to so the job.
To test, you can run:
$ otool -L *.so
in the matplotlib directory that is buried in the build directory. it
will tell you what libs the matplotlib extensions are linked to. They
should not be linked to libfreetype or libpng. libz is OK, it's included
with the stock OS-X.
Once you've got that built right, you can make an installer package with
Py2App.
This is a note from Bob Ippolito on the macPython mailing list:
"""use bdist_mpkg from py2app to make a redistributable .pkg installer
for it. After installing py2app, you should have a tool in
/usr/local/bin called "bdist_mpkg" that will Just Do It without any
setup.py modifications to the target lib... so go into the matplotlib
directory, type bdist_mpkg, and cross your fingers that a
dist/matplotlib-xx.pkg
"""
Here's exactly what I tried:
In the matplotlib directory (the same place as setup.py)
$ bdist_mpkg
and it worked!
Note: there are occasionally troubles with installing a newer matplotlib
over an older one. You may want to remove an older version before
installing, if you have one. To do this, delete:
/Library/Python/2.3/matplotlib/
Then click the mpkg. to install.
Building with tcl/TK:
I downloaded the BI (Batteries Included) installer for tcl/Tk Aqua. It's
got a lot of stuff I don't need, but it's only disk space. I then used
the MacPython PackageManager and the standard package list, and
installed Tkinter from there. It seemed to work.
Now back to the build cycle...Yeah it works!
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...
From: Chris B. <Chr...@no...> - 2005年06月08日 22:24:24
Charles Moad wrote:
> Installing each
> dependency would probably be just as easy as trying to use components
> from my installer.
I put instructions for how to do this in my package for OS-X-10.3, 
py2.3.0. Here they are. If you do all this, you can donate the package 
to Bob's repository on pythonmac.org.
There is a related thread about defining a standard way to do this for 
matplotlib, so it will build out of the box.
They should work just fine for newer versions of OS, matplotlib, and 
python. Sorry they are a bit wordy:
Installing matplotlib on OS-X (10.3.7)
Here are my notes as to what it took to get matplotlib (0.71) installed 
and working on OS-X. I have so far kept a fink-free system, so that's 
what I've done here as well. I use it with the AGG back end for 
generating images for a web site, and hopefully with the wx backend for 
interactive use and embedding in wx Applications. I've also quickly got 
it working with TK. Note that this is kind of a running commentary, not 
well edited. I'd read the whole thing before starting.
1) Requirements:
-------------------------------------------
According to the matplotlib install docs 
(http://matplotlib.sourceforge.net/installing.html), you need the following:
freetype (>= 2.1.7)
libpng
zlib
Personally, I've been avoiding Fink, as it doesn't seem to play well 
with the rest of OS-X, including the Apple supplied Python, so I've 
looked elsewhere for these libs.
a) Freetype:
I seem to have it in:
/usr/X11R6/include/freetype2
I don't think I installed it myself, so it probably came with Apple's 
X11, Which I did install.
However, I seemed to be having problems with that version, so I looked, 
and it seems to be:
libfreetype.6.3.dylib
Given that freetype2 is currently at version 2.1.9, I have no idea what 
to make of that! So off to sourceforge to get a new freetype:
http://freetype.sourceforge.net/index2.html
where I got:
freetype-2.1.9.tar.gz
Following the instructions in docs/INSTALL.UNX:
$ ./configure
$ make
$ sudo make install
That puts it in /usr/local/..., which is a good place for it.
NOTE: The above will build freetype as a shared library, which is fine 
if you are building ot run on the same system you are building on. 
However, if you want to buuild a re-distributable package, you'll need a 
static library, which you can get by doing:
$ ./configure --disable-shared --enable static
$ make
$ sudo make install
Hmm. that made the static libs (*.a) , but also the dynamic ones.
Make sure to do:
$ make clean
if you had already built it. You may also have to remove the shared 
libs, so that they won't be found (*.dyld). I had to remove them from 
/usr/local/lib.
b) zlib:
I have:
/usr/include/zlib.h
I don't know where I might have gotten it, but there it is.
NOTE: I checked on another system in my office, and it doesn't have 
zlib. It does, however have libz, which I am told is the same thing, to 
you shouldn't need this.
c) libpng:
This, I didn't have on my system, except inside the wxWidgets source 
tree, so I went looking for it.
Note that you need zlib to compile libpng, so make sure you have that first.
I did a google search for "libpng OS-X". I found:
http://www.libpng.org/pub/png/pngcode.html
Which led me to the libpng sourceforge site.
 From there I downloaded:
libpng-1.2.8.tar.gz
unpacked it, and opened a terminal in the libpng-1.2.8 directory, and did:
$ cp scripts/makefile.darwin ./makefile
(note that according to the INSTALL, there is supposed to be a 
makefile.macosx, but it wasn't there)
I took a look in the makefile, and found:
ZLIBLIB=/usr/local/lib
ZLIBINC=/usr/local/include
Which is not where zlib is on my system. However, while I can find 
zlib.h, I couldn't fine the actual lib, so I tried make without changing 
anything.
$ make
Which seemed to work fine. zlib must be installed in a standard 
location, and gcc found it.
$ sudo make install
to install the lib into /usr/local/ (this was specified in the makefile, 
and it's a good place for it)
$ make test
and
$ ./pngtest pngnow.png
Which both seemed to pass.
If you want to build a re-distributable version of matplotlib, you need 
the static version of libpng, instead of the dynamic one. It doesn't use 
./configure, so instead, I did a:
sudo make install-static
and that installed the *.a files in /usr/local/lib.
d) Numeric or numarray:
I already have Numeric installed, from Bob Ippolito's PIMP (MacPython 
Package Manager) repostitory. (www.undefined.org/python)
2) Building matplotlib
---------------------------------------------------------
First, I took a look at the matplotlib setup.py. It had "auto" for the 
back-end flags, so I thought I would give it a try that way:
$python setup.py build
If you have only the static version of libpng and libfreetype (*.a, and 
not *.dylib) in /usr/local/lib (or anywhere else on your lib search 
path), then it should link those statically.
That worked!
$ sudo python setup.py install
4) And now to test!
$python
 >>> import pylab
Could not open font file /Library/Fonts/NISC18030.ttf
No module named pygtk
PyGTK version 1.99.16 or greater is required to run the GTK Matplotlib 
backends
This turns out to be because the matlabrc file sets the GTKAgg back end 
as the default. You have two choices.
1) you can set the back end before importing pylab.
 >>> import matplotlib
 >>> matplotlib.use('Agg')
 >>> import pylab
This works fine
2) Edit the matplotlibrc file. I found it in:
/System/Library/Frameworks/Python.framework/Versions/2.3/share/matplotlib/.matplotlibrc
Change the line:
backend : GTKAgg # the default backend
to
backend : Agg # the default backend
And you're all set to make images for the web, etc.
I'm going to leave getting it to work with wxPython for another day.
3) Building a matplotlib Binary Package for OS-X:
First you need to make sure you've got libpng and libfreetype staticaly 
linked. I did this by copying the headers and *.a files for them into a 
directory I created called "StaticLibs", in the main matplot lib 
directory (the one setup,py is in). You could just as easily put in 
links, rather than copies, probably a better idea, actually.
Then I edited setupext.py, so that distutils would only look there:
basedir = {
 'win32' : ['win32_static',],
 'linux2' : ['/usr/local', '/usr',],
 'linux' : ['/usr/local', '/usr',],
# 'darwin' : ['/usr/local', '/usr', '/sw', '/usr/X11R6'],
 'darwin' : ['StaticLibs'],
 'freebsd4' : ['/usr/local', '/usr'],
 'sunos5' : [os.getenv('MPLIB_BASE') or '/usr/local',],
}
I'm talking to John Hunter about having a conditional Static setup in 
the official setup.py to support this. This seemed to so the job.
To test, you can run:
$ otool -L *.so
in the matplotlib directory that is buried in the build directory. it 
will tell you what libs the matplotlib extensions are linked to. They 
should not be linked to libfreetype or libpng. libz is OK, it's included 
with the stock OS-X.
Once you've got that built right, you can make an installer package with 
Py2App.
This is a note from Bob Ippolito on the macPython mailing list:
"""use bdist_mpkg from py2app to make a redistributable .pkg installer 
for it. After installing py2app, you should have a tool in 
/usr/local/bin called "bdist_mpkg" that will Just Do It without any 
setup.py modifications to the target lib... so go into the matplotlib 
directory, type bdist_mpkg, and cross your fingers that a 
dist/matplotlib-xx.pkg
"""
Here's exactly what I tried:
In the matplotlib directory (the same place as setup.py)
$ bdist_mpkg
and it worked!
Note: there are occasionally troubles with installing a newer matplotlib 
over an older one. You may want to remove an older version before 
installing, if you have one. To do this, delete:
/Library/Python/2.3/matplotlib/
Then click the mpkg. to install.
Building with tcl/TK:
I downloaded the BI (Batteries Included) installer for tcl/Tk Aqua. It's 
got a lot of stuff I don't need, but it's only disk space. I then used 
the MacPython PackageManager and the standard package list, and 
installed Tkinter from there. It seemed to work.
Now back to the build cycle...Yeah it works!
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...
From: Chris B. <Chr...@no...> - 2005年06月08日 18:48:57
John Hunter wrote:
> If either of you have a diff against setup*.py that will make mpl src
> builds on these systems work better, I'll fold them into the main
> line.
I had intended to do this, but before I do, I think theres a need for a 
little discussion.
Charles and I have taken two different approaches to dealing with the 
dependencies not included in stock OS-X:
libpng
libfreetype
(as noted by Charles, libfreetype does seem to exist, in some form with 
Apple's X11 implementation, but neither of us could get it to work)
The way I handled these libs was to build them as static libs, install 
them inside the matplotlib build tree, then alter the setup.py so that 
it would use the statically linked versions. This resulted in a simple 
stand-alone binary, that is easy to install. However, you do need to put 
those static libs in the right place before you can build, so I wasn't 
sure we'd want to hard-code that into the stock setup.py. You do need to 
resolve the dependencies in some way in any case, so maybe it's not a 
bad idea.
My understanding is that Charles took an alternative approach: providing 
libpng and libfreetype as OS-X Frameworks, and building matplotlib 
against those. This is really the way it "should" be done on OS-X. 
However, it seems a little harder to set up to me (unless the libs in 
question work with a --framework flag to make. I spend a lot more time 
on Linux, so all this is a bit of a mystery to me.) It also strikes me 
as a little harder to make a package out of, as you've got multiple 
things to install and bdist_mpkg won't just do it for you.
What are other's thoughts about the best way to do this? It would be 
nice to have a standard approach built into the matplotlib setup.py.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...
From: Werner F. B. <wer...@fr...> - 2005年06月08日 16:04:04
Attachments: toolbartest.png
Hi John,
John Hunter wrote:
>>>>>>"andrea" == andrea gavana <and...@ti...> writes:
> 
> 
> andrea> Hello John & NG, I have just downloaded matplotlib 0.81,
> andrea> and I am having some problems with the ToolBar. The "Back"
> andrea> and "Forward" icons in the ToolBar2 are not shown. The
> andrea> buttons are completely grey and they seem inactive. Is
> andrea> this the expected behavior? I think it is not. However,
> andrea> my configuration is:
> 
> andrea> - Windows XP - wxPython 2.6.1.0 - MatPlotLib 0.81 - WXAgg
> andrea> backend - ToolBar2
> 
> This is a feature and a bug. The feature part is that Werner Bruhin
> added a patch to "gray out" the forward and back buttons when clicking
> them produces no effect. Eg, if there is no back (your first view of
> the figure) the button should be grayed out. If you navigate
> somewhere, the button will be enabled.
Just did a little test with the back.png file - see attached it shows in 
black and white if it is NOT enabled.
However here stops the good news, I can't figure out what needs to be 
changed in matplotlib to get the same result. Hacked "_load_bitmap2" 
which used the "png" file but then I get the normal image instead of the 
black and white one.
I'll keep looking, but if anyone has an idea it will be very welcome.
See you
Werner
> 
> The bug is that on win32 with wxpython 2.6.1 instead of presenting a
> grayed out version of the button the button is a solid gray rectangle,
> and it is visually very disturbing to see it toggle between an arrow
> and a gray rectangle. On linux with wx 2.5.3, the arrow button still
> looks like an arrow, but is gray to indicate "not enabled"
> 
> Does this feature work properly for anyone on windows? Other
> WX/Windows users, please send me your wxpython version numbers and let
> me know if this is working for you so we can file a bug report to the
> wx list. You can get your wxpython version by running your script
> with 
> 
> > python myscript.py -dWXAgg --verbose-helpful
> 
> Thanks!
> JDH
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
> a projector? How fast can you ride your desk chair down the office luge track?
> If you want to score the big prize, get to know the little guy. 
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
From: Fernando P. <Fer...@co...> - 2005年06月08日 15:43:45
Attachments: bboxes.tgz
Darren Dale wrote:
> On Wednesday 08 June 2005 1:29 am, Fernando Perez wrote:
> 
>>Hi all,
>>
>>I'm enjoying the new toy (real LaTeX support), and after running the
>>examples/tex_demo, I noticed the bounding boxes aren't quite right.
> 
> Which version of ghostscript are you using? We had trouble with bboxes using a 
> version older than ghostscript-8.16. 
Ah, that could be it. Fedora 3 comes stock with:
[~]> rpm -qa | grep ghost
ghostscript-fonts-5.50-13
ghostscript-7.07-33
> I use ghostscript's epswrite device to convert a latex-generated postscript to 
> eps. It converts the fonts to bitmaps, as you pointed out, but you can 
> increase the resolution in rc with ps.distiller.res: I have it set to 6000, 
> and the files are not too big.
Mh, I dind't point that out: I didn't even know you could do it :)
> Would you send me a copies of the bad eps and the fixed version, and also a 
> copy of ps2eps? I don't have that program on my system, and was not able to 
> find it on the web.
Here goes. As it turns out, ps2eps is a simple perl script which I got god 
knows when. So people won't actually have it on their systems, it's something 
that lives in /usr/local/bin on my box, sorry.
But no worries. I can lie with using ps2eps for now, until I can upgrade to a 
moer current ghostscript.
Cheers,
f
From: Werner F. B. <wer...@fr...> - 2005年06月08日 15:35:41
John Hunter wrote:
>>>>>>"andrea" == andrea gavana <and...@ti...> writes:
> 
> 
> andrea> Hello John & NG, I have just downloaded matplotlib 0.81,
> andrea> and I am having some problems with the ToolBar. The "Back"
> andrea> and "Forward" icons in the ToolBar2 are not shown. The
> andrea> buttons are completely grey and they seem inactive. Is
> andrea> this the expected behavior? I think it is not. However,
> andrea> my configuration is:
> 
> andrea> - Windows XP - wxPython 2.6.1.0 - MatPlotLib 0.81 - WXAgg
> andrea> backend - ToolBar2
> 
> This is a feature and a bug. The feature part is that Werner Bruhin
> added a patch to "gray out" the forward and back buttons when clicking
> them produces no effect. Eg, if there is no back (your first view of
> the figure) the button should be grayed out. If you navigate
> somewhere, the button will be enabled.
Not guilty here, at least not on purpose, someone else might have put in 
a patch to enable/disable the buttons. But in the disabled state they 
should still show the black and white version (using the alpha channel).
I looked at it when I saw Andrea's post but can't figure out why they 
show a grey block instead of a black and white version of the button.
This is a problem I do have on the Win 2000 with my own app/images, but 
on XP the alpha channel stuff works correctly.
I'll have another look at it.
See you
Werner
> 
> The bug is that on win32 with wxpython 2.6.1 instead of presenting a
> grayed out version of the button the button is a solid gray rectangle,
> and it is visually very disturbing to see it toggle between an arrow
> and a gray rectangle. On linux with wx 2.5.3, the arrow button still
> looks like an arrow, but is gray to indicate "not enabled"
> 
> Does this feature work properly for anyone on windows? Other
> WX/Windows users, please send me your wxpython version numbers and let
> me know if this is working for you so we can file a bug report to the
> wx list. You can get your wxpython version by running your script
> with 
> 
> > python myscript.py -dWXAgg --verbose-helpful
> 
> Thanks!
> JDH
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
> a projector? How fast can you ride your desk chair down the office luge track?
> If you want to score the big prize, get to know the little guy. 
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
From: John H. <jdh...@ac...> - 2005年06月08日 15:16:53
>>>>> "andrea" == andrea gavana <and...@ti...> writes:
 andrea> Hello John & NG, I have just downloaded matplotlib 0.81,
 andrea> and I am having some problems with the ToolBar. The "Back"
 andrea> and "Forward" icons in the ToolBar2 are not shown. The
 andrea> buttons are completely grey and they seem inactive. Is
 andrea> this the expected behavior? I think it is not. However,
 andrea> my configuration is:
 andrea> - Windows XP - wxPython 2.6.1.0 - MatPlotLib 0.81 - WXAgg
 andrea> backend - ToolBar2
This is a feature and a bug. The feature part is that Werner Bruhin
added a patch to "gray out" the forward and back buttons when clicking
them produces no effect. Eg, if there is no back (your first view of
the figure) the button should be grayed out. If you navigate
somewhere, the button will be enabled.
The bug is that on win32 with wxpython 2.6.1 instead of presenting a
grayed out version of the button the button is a solid gray rectangle,
and it is visually very disturbing to see it toggle between an arrow
and a gray rectangle. On linux with wx 2.5.3, the arrow button still
looks like an arrow, but is gray to indicate "not enabled"
Does this feature work properly for anyone on windows? Other
WX/Windows users, please send me your wxpython version numbers and let
me know if this is working for you so we can file a bug report to the
wx list. You can get your wxpython version by running your script
with 
 > python myscript.py -dWXAgg --verbose-helpful
Thanks!
JDH
From: John H. <jdh...@ac...> - 2005年06月08日 15:12:22
>>>>> "Nicolas" == Nicolas Girard <nic...@ne...> writes:
 Nicolas> Hi all, I find ytitle() to behave quite strangely ; the
 Nicolas> first link points to a figure to each left subplot of
 Nicolas> which I used
 Nicolas> ylabel(labl)
 Nicolas> and on the figure pointed by the second link I used
 Nicolas> text(-0.07,0.5,labl,verticalalignment='center',
 Nicolas> rotation='vertical',transform=gca().transAxes,clip_on=False)
 Nicolas> http://nicolasgirard.nerim.net/ytitle.jpg
 Nicolas> http://nicolasgirard.nerim.net/text.jpg
 Nicolas> from these 2 samples it seems like ytitle()'s behaviour
 Nicolas> is odd, or at least not optimal. What do you think ?
Which backend are you using? It could be a backend specific bug. From
the fact that you are making jpg images, my guess is you are using GTK
or WX. Unless you have good reason not to, I would advise you to use
GTKAgg/WXAgg and output PNG. PNG is a much better format for line art
and text.
Do you see the extra horizontal space in *Agg or PS backends? Note
also that the space between the yticklabels and the ylabel is
controlled by ax.yaxis.LABELPAD, which defaults to 5 points. Also,
are you using mathtext or rc.usetex=True? 
When reporting problems, it is very helpful to
 1) run your script with --verbose-helpful and report the output
 2) indicated any nondefault rc options (rc.usetex?)
 3) attach a standalone script we can run, if possible
This will save me a lot of guessing and typing.
Thanks!
JDH
From: Matt N. <new...@ca...> - 2005年06月08日 14:28:15
Darren, Fernando,
I'm sorry I haven't had a chance to try out the new tex/latex
support, and am really looking forward to it. Thanks!!
I've used scripts to convert gnuplot/ps-latex to eps and png for
too many years (and will be thrilled to replace them with
matplotlib scripts). For the EPS bbox problem from dvips, I've
had good luck running
 gs -q -dBATCH -dNOPAUSE -sDEVICE=bbox my.eps
on the eps file generated from 
 dvips -E ... -o my.eps my.dvi 
The bbox output from 'gs -sDEVICE=bbox' can then be used to
rewrite the eps file. It's definitely a kludge and involves
temporary files (this might be unavoidable, and tex/latex uses
lots of these anyway), but the results seem good, even with
relatively old versions of ghostscript.
I don't know if that's better than Fernando's suggestion or not,
but since the PS backend already uses gs (I think), it might be
worth considering.
Thanks!
--Matt
PS: For eps->png, I've been quite happy running 
 convert -antialias -density 300 my.eps my.png
Maybe that's a reasonable alternative to dvipng??
From: Darren D. <dd...@co...> - 2005年06月08日 12:50:49
On Wednesday 08 June 2005 1:29 am, Fernando Perez wrote:
> Hi all,
>
> I'm enjoying the new toy (real LaTeX support), and after running the
> examples/tex_demo, I noticed the bounding boxes aren't quite right.
Hi Fernando,
Which version of ghostscript are you using? We had trouble with bboxes usin=
g a=20
version older than ghostscript-8.16.=20
I use ghostscript's epswrite device to convert a latex-generated postscript=
 to=20
eps. It converts the fonts to bitmaps, as you pointed out, but you can=20
increase the resolution in rc with ps.distiller.res: I have it set to 6000,=
=20
and the files are not too big.
Would you send me a copies of the bad eps and the fixed version, and also a=
=20
copy of ps2eps? I don't have that program on my system, and was not able to=
=20
find it on the web.
Thanks,
Darren
From: Nicolas G. <nic...@ne...> - 2005年06月08日 11:36:56
Hi all,
I find ytitle() to behave quite strangely ; the first link points to a figure 
to each left subplot of which I used
 ylabel(labl)
and on the figure pointed by the second link I used
 text(-0.07,0.5,labl,verticalalignment='center',
 rotation='vertical',transform=gca().transAxes,clip_on=False)
http://nicolasgirard.nerim.net/ytitle.jpg
http://nicolasgirard.nerim.net/text.jpg
from these 2 samples it seems like ytitle()'s behaviour is odd, or at least 
not optimal. What do you think ?
cheers,
nicolas
From: Fernando P. <Fer...@co...> - 2005年06月08日 05:30:21
Hi all,
I'm enjoying the new toy (real LaTeX support), and after running the 
examples/tex_demo, I noticed the bounding boxes aren't quite right. I know 
that Darren and John have struggled a lot with this issue, and I don't know 
what the true solution should be. But I've seen similar problems in the past 
with Gnuplot (when making square aspect ratio plots), and I had this lying around:
def eps_fix_bbox(fname):
 """Fix the bounding box of an eps file by running ps2eps on it.
 If its name ends in .eps, the original file is removed.
 This is particularly useful for plots made by Gnuplot with square aspect
 ratio: there is a bug in Gnuplot which makes it generate a bounding box
 which is far wider than the actual plot.
 This function assumes that ps2eps is installed in your system."""
 # note: ps2ps and eps2eps do NOT work, ONLY ps2eps works correctly. The
 # others make output with bitmapped fonts, which looks horrible.
 print 'Fixing eps file: <%s>' % fname
 xsys('ps2eps -f -q -l %s' % fname)
 if fname.endswith('.eps'):
 os.rename(fname+'.eps',fname)
those of you running IPython can get it simply via:
from IPython.Gnuplot2 import eps_fix_bbox
I don't claim that it does the right thing everywhere, but a few tests seemed 
to give reasonable results. I don't know if it will help others, but it works 
for me, so here it goes.
Cheers,
f
From: Charles M. <cm...@in...> - 2005年06月08日 00:43:45
	I believe I said I would make a pkg for OS 10.4, not python 2.4.1.
Sorry if I said the later. I am waiting a little while now, since it
seems 0.81 is having tex issues and there may be a version bump here soon.
	I could help you through the install you mentioned. Installing each
dependency would probably be just as easy as trying to use components
from my installer. There is nothing stopping you from choosing a
customized install from the tiger installer to install just freetype and
libpng. You have to make a few small edits to setup.py to make it work
with those.
- Charlie
fgh...@bl... wrote:
> Thanks to everybody for the informative replies!
> 
> I'm now trying to decide
> my best course of action. The way I see the current situation, there is Charlie's
> standalone installer from IU, but that does not integrate with the pythonmac.org
> installation (which currently affects me greatly, because I'm running Tiger
> and the pythonmac.org 2.4.1 "framework"). Then there is the pythonmac installer,
> which puts stuff into the Apple installation of 2.3.... 
> 
> I've tried a few
> obvious things (like soft-linking the pythonmac 2.3 matplotlib directory under
> its site-packages to the 2.4.1 pythonmac.org's site-packages), but nothing
> has worked yet.
> 
> IIRC, Charlie(?) said in an earlier post that he was going
> to build against 2.4.1 and post the results (to the IU website?) once he got
> home to a machine with 2.4.1 on it. It seems to me that this should solve
> my problem, but I might be missing something, and hence need to compile from
> source. Not a big deal at all for the python stuff (hooray for setup.py! ;-)
> but I would then need to fight 'dependency hell' for all of the missing libraries
> from my installations. I was kind of hoping to find that someone else had
> already won that battle! ;-)
> 
> Should it come down to that, I'd be happy
> to post any sucess stories from my ham-fisted attempts to build the .dmg anywhere
> that it useful to the wider community.
> 
> To recap: for pythonmac.org 2.4.1
> users there does not seem to exist a usable installer for matplotlib. 
> 
> 
> 
> --- Charles Moad <cm...@in... wrote:
> 
>> All the binaries I provide
> 
> depend on the system installed python 
> 
>>(i.e. python2.3.x). These binaries
> 
> are meant for people who want a 
> 
>>one click installer for matplotlib in
> 
> OSX that includes all needed 
> 
>>dependencies. I would expect more seasoned
> 
> python users to install 
> 
>>the packages from pythonmac.org. I will add
> 
> a note on the site.
> 
>> For the record, if anyone wants the Xcode project
> 
> files for the 
> 
>>freetype and libpng frameworks I provide, just ask.
>>
> 
> 
>>- Charlie
>>
>>On Jun 7, 2005, at 4:28 PM, Chris Barker wrote:
>>
>>
>>>
>>>Charles Moad wrote:
>>>
>>>
>>>> I am posting a new 0.81 build
> 
> with basemap-0.5 right now for 
> 
>>>>Panther.
>>>>
>>>
>>>But does this
> 
> use python 2.4 ? That wasn't' clear to me from the 
> 
>>>download page.
>>>
>>>- Chris
>>>-- 
>>>Christopher Barker, Ph.D.
>>>Oceanographer
> 
> 
>>>NOAA/OR&R/HAZMAT (206) 526-6959 voice
>>>7600 Sand Point
> 
> Way NE (206) 526-6329 fax
> 
>>>Seattle, WA 98115 (206) 526-6317
> 
> main reception
> 
>>>Chr...@no...
>>>
>>>
>>>-------------------------------------------------------
> 
> 
>>>This SF.Net email is sponsored by: NEC IT Guy Games. How far can 
>>>you shotput
>>>a projector? How fast can you ride your desk chair down
> 
> the office 
> 
>>>luge track?
>>>If you want to score the big prize, get
> 
> to know the little guy. 
> 
>>>Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> 
> 
>>>_______________________________________________
>>>Matplotlib-users
> 
> mailing list
> 
>>>Mat...@li...
>>>https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
>>_______________________________________________
>>Pythonmac-SIG
> 
> maillist - Pyt...@py...
> 
>>http://mail.python.org/mailman/listinfo/pythonmac-sig
> 
> 

Showing 13 results of 13

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /