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
(1) |
2
(10) |
3
(29) |
4
(56) |
5
(44) |
6
(26) |
7
(12) |
8
(1) |
9
(2) |
10
(11) |
11
(28) |
12
(17) |
13
(6) |
14
(17) |
15
(7) |
16
(1) |
17
(8) |
18
(8) |
19
(7) |
20
(2) |
21
(8) |
22
(4) |
23
(6) |
24
(1) |
25
(2) |
26
(8) |
27
(3) |
28
(5) |
29
(1) |
30
|
31
(1) |
|
|
|
|
|
[Fairly new at matplotlib, but very happy with it so far] Is it possible to retrieve images rendered by one of the backends as an object, rather than just saving to a file? Specifically, I need to render graphs to SVG code, that I can turn into a DOM object for further manipulation. I can save to a temp file and immediately reload it into a DOM, but that is cumbersome in a single program. The only place I can see to generate rendered output is savefig(). There is a reference in the documentation to using a file-like object with the Cairo backend. Is that the only possibility? If so, any ideas on a workaround other than temp files? -- View this message in context: http://www.nabble.com/rendered-objects-%28esp.-SVG%29-tf4952354.html#a14180802 Sent from the matplotlib - users mailing list archive at Nabble.com.
Hello, On the Mac I use TkAgg and can output PDF files no problem. The only reason I was using GTKCairo was to get the PDF output which was not working with GTKAgg. I just updated to the most recent SVN from the one I was using from earlier today and now I can save to PDF in GTKAgg without troubles. Basically I just wanted something that was interactive till I made the plot to my liking then I could save the figure to a PDF. On the mac this worked with TkAgg without any troubles and now on Linux it works iwth GTKAgg without any troubles. Not sure what changed but thanks for the help. Regards, Brian On Dec 5, 2007, at 4:01 PM, Michael Droettboom wrote: > Sorry for the wild goose chase. Now that my memory has been jogged > -- This is actually a known problem with the Cairo backend. Cairo > only allows access to fonts installed in the normal OS-specific > places (and /usr/lib/python2.5/site-packages/matplotlib/mpl-data/ > fonts/ttf is definitely not one of them... ;) Worse than that, > AFAIK, there is know way of knowing whether a particular font was > found, so we can't give users a nice warning message when your > situation occurs. > > To remedy: Install all of the matplotlib fonts into a standard > place where fontconfig will find them (such as ~/.fonts). Then run > fc-cache to regenerate the font cache. Matplotlib's Cairo backend > should hopefully work after that. > > You can also use the regular PDF backend, which doesn't exhibit this > problem. If there's a reason why the Cairo PDF output is better > than the normal PDF backend's output for you, please let us know. > > What I'm puzzled by now is -- why did the Cairo backend work for you > on the Mac? Did you install the fonts there? I'm not on the Mac > much --- but I'd be very surprised if Cairo found the CM fonts as > installed by matplotlib automagically there. > > Cheers, > Mike > > Brian Baughman wrote: >> Hello, >> Below is the requested output which looks correct to me: >> brian@loki:~/dev/pyanalysis$ python >> Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32) >> [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 >> Type "help", "copyright", "credits" or "license" for more >> information. >> >>> import matplotlib >> >>> matplotlib.__file__ >> '/usr/lib/python2.5/site-packages/matplotlib/__init__.pyc' >> >>> matplotlib.__version__ >> '0.91.2svn' >> >>> matplotlib._get_data_path() >> '/usr/lib/python2.5/site-packages/matplotlib/mpl-data' >> Deleting the ~/.matplotlib/fontManager.cache did not change the >> behavior. Thanks for all the help. I really like using matplotlib >> on my Mac but it doesn't have the power that my Ubuntu box has. >> Regards, >> Brian >> On Dec 5, 2007, at 2:52 PM, Michael Droettboom wrote: >>> What's happening is that it isn't finding the Bakoma Computer >>> Modern fonts. These have a non-standard encoding, so the '-' for >>> instance, is actually under a different character code. >>> >>> So... we need to track down why it's looking in the wrong place. >>> >>> Can you send the output of: >>> >>> > python >>> Python 2.5.1 (r251:54863, Jul 2 2007, 08:53:40) >>> [GCC 3.4.6 20060404 (Red Hat 3.4.6-8)] on linux2 >>> Type "help", "copyright", "credits" or "license" for more >>> information. >>> >>> import matplotlib >>> >>> matplotlib.__file__ >>> '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/ >>> __init__.pyc' >>> >>> matplotlib.__version__ >>> '0.91.2.svn' >>> >>> matplotlib._get_data_path() >>> '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/mpl-data' >>> >>> >>> >>> You may also try deleting your font cache in ~/.matplotlib/ >>> fontManager.cache >>> >>> Cheers, >>> Mike > > -- > Michael Droettboom > Science Software Branch > Operations and Engineering Division > Space Telescope Science Institute > Operated by AURA for NASA
Sorry for the wild goose chase. Now that my memory has been jogged -- This is actually a known problem with the Cairo backend. Cairo only allows access to fonts installed in the normal OS-specific places (and /usr/lib/python2.5/site-packages/matplotlib/mpl-data/fonts/ttf is definitely not one of them... ;) Worse than that, AFAIK, there is know way of knowing whether a particular font was found, so we can't give users a nice warning message when your situation occurs. To remedy: Install all of the matplotlib fonts into a standard place where fontconfig will find them (such as ~/.fonts). Then run fc-cache to regenerate the font cache. Matplotlib's Cairo backend should hopefully work after that. You can also use the regular PDF backend, which doesn't exhibit this problem. If there's a reason why the Cairo PDF output is better than the normal PDF backend's output for you, please let us know. What I'm puzzled by now is -- why did the Cairo backend work for you on the Mac? Did you install the fonts there? I'm not on the Mac much --- but I'd be very surprised if Cairo found the CM fonts as installed by matplotlib automagically there. Cheers, Mike Brian Baughman wrote: > Hello, > > Below is the requested output which looks correct to me: > brian@loki:~/dev/pyanalysis$ python > Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32) > [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import matplotlib > >>> matplotlib.__file__ > '/usr/lib/python2.5/site-packages/matplotlib/__init__.pyc' > >>> matplotlib.__version__ > '0.91.2svn' > >>> matplotlib._get_data_path() > '/usr/lib/python2.5/site-packages/matplotlib/mpl-data' > > Deleting the ~/.matplotlib/fontManager.cache did not change the > behavior. Thanks for all the help. I really like using matplotlib on > my Mac but it doesn't have the power that my Ubuntu box has. > > Regards, > Brian > > On Dec 5, 2007, at 2:52 PM, Michael Droettboom wrote: > >> What's happening is that it isn't finding the Bakoma Computer Modern >> fonts. These have a non-standard encoding, so the '-' for instance, >> is actually under a different character code. >> >> So... we need to track down why it's looking in the wrong place. >> >> Can you send the output of: >> >> > python >> Python 2.5.1 (r251:54863, Jul 2 2007, 08:53:40) >> [GCC 3.4.6 20060404 (Red Hat 3.4.6-8)] on linux2 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> import matplotlib >> >>> matplotlib.__file__ >> '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/__init__.pyc' >> >>> matplotlib.__version__ >> '0.91.2.svn' >> >>> matplotlib._get_data_path() >> '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/mpl-data' >> >>> >> >> You may also try deleting your font cache in >> ~/.matplotlib/fontManager.cache >> >> Cheers, >> Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA
I'm on a Linux box (I'm assuming you're on Windows, since you mentioned Process Explorer), and I wasn't able to find any file handle "leaks", as such, but I did see that font files were being opened many more times than they need to be. If you're able to run from Subversion, r4633 has a fix for this. I'm curious if it fixes your symptoms. Cheers, Mike Jörgen Stenarson wrote: > hi, > > I think the new 0.91.1 has some kind of file handle leak at least when > using python 2.4, tkagg, and within ipython. Using process explorer to > look at filehandles opened by python then I get about 25 new open > handles to vera.ttf per %run of the following script. > > from pylab import * > > figure(1) > clf() > title("jj") > figure(2) > clf() > title("jj") > > > However if I close("all") between %runs then all the open handles are > closed. > > I tried the same thing with 0.90.1 and then I only get 2 handles for the > same script and no increase on subsequent calls with or without > close("all"). > > /Jörgen > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA
I feel a 0.91.2 in the next few weeks, and I'll be sure to do this and send you a test build. - Charlie On Dec 5, 2007 1:30 PM, Russell E Owen <ro...@ce...> wrote: > At 10:03 AM -0800 2007年12月05日, Christopher Barker wrote: > >Russell E Owen wrote: > >>At 10:08 AM -0500 2007年12月05日, Stephen Uhlhorn wrote: > >>>Just for my edification, why can't the egg version be linked > >>>against/include a different Tcl/Tk? > >> > >>If you mean why can't it be built that way in the first place, I > >>don't know. The guy who builds it apparently doesn't read this list, > > > >Sure he does (if you mean the matplotlib list), and he did ask about > >it right before this release. Maybe that was asked on > >matplotlib-devel though (I filter them to the same place). > > It was on matploblib-devel. I'll start skimming that newsgroup. > > >>I suspect the official egg can somehow be patched, but I find it > >>easier to just build my own and put that on pythonmac. > > > >Ideally, there would be only one binary version, and it would work > >with either Tcl/Tk. Is that possible? or is this like the old wx > >situation, where it can only be run with the same version it is > >built against. Arrggg! I hope not. > > The version I build *can* be used with the built in Tcl/Tk. The > version Charlie Moad builds cannot be used with TkAgg and a 3rd party > Tcl/Tk -- it not only won't use the library, but it also acts flaky. > Older versions crashed. 0.91.1 doesn't crash, but import of pylab > fails with a traceback. > > For some reason it seems to be necessary to have a 3rd party Tcl/Tk > installed when building matplotlib. It seems a shame. Tkinter in > Python 2.4 was the same way, but that got fixed in Python 2.5 (I > don't whether the installer got fixed or whether whoever builds Mac > Python 2.5 installed a 3rd party Tcl/Tk). > > >If there really do need to be two, then they should be labeled > >somehow, and both be up on python mac. > > Since there don't need to be two versions this is not necessary. > > However, Charlie Moad appears to be willing to start building a > version that works with 3rd party Tcl/Tk. I really hope that happens. > > -- Russell > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
Hello, Below is the requested output which looks correct to me: brian@loki:~/dev/pyanalysis$ python Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import matplotlib >>> matplotlib.__file__ '/usr/lib/python2.5/site-packages/matplotlib/__init__.pyc' >>> matplotlib.__version__ '0.91.2svn' >>> matplotlib._get_data_path() '/usr/lib/python2.5/site-packages/matplotlib/mpl-data' Deleting the ~/.matplotlib/fontManager.cache did not change the behavior. Thanks for all the help. I really like using matplotlib on my Mac but it doesn't have the power that my Ubuntu box has. Regards, Brian On Dec 5, 2007, at 2:52 PM, Michael Droettboom wrote: > What's happening is that it isn't finding the Bakoma Computer Modern > fonts. These have a non-standard encoding, so the '-' for instance, > is actually under a different character code. > > So... we need to track down why it's looking in the wrong place. > > Can you send the output of: > > > python > Python 2.5.1 (r251:54863, Jul 2 2007, 08:53:40) > [GCC 3.4.6 20060404 (Red Hat 3.4.6-8)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import matplotlib > >>> matplotlib.__file__ > '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/__init__.pyc' > >>> matplotlib.__version__ > '0.91.2.svn' > >>> matplotlib._get_data_path() > '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/mpl-data' > >>> > > You may also try deleting your font cache in ~/.matplotlib/ > fontManager.cache > > Cheers, > Mike
What's happening is that it isn't finding the Bakoma Computer Modern fonts. These have a non-standard encoding, so the '-' for instance, is actually under a different character code. So... we need to track down why it's looking in the wrong place. Can you send the output of: > python Python 2.5.1 (r251:54863, Jul 2 2007, 08:53:40) [GCC 3.4.6 20060404 (Red Hat 3.4.6-8)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import matplotlib >>> matplotlib.__file__ '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/__init__.pyc' >>> matplotlib.__version__ '0.91.2.svn' >>> matplotlib._get_data_path() '/home/mdroe/usr/lib/python2.5/site-packages/matplotlib/mpl-data' >>> You may also try deleting your font cache in ~/.matplotlib/fontManager.cache Cheers, Mike Brian Baughman wrote: > Hello, > > I am using matplotlib svn 4626 and Cairo 1.4.0 all with python 2.5 with > Ubuntu linux 7.10. The only lines in my matplotlibrc file which are > uncommented are: > backend : GTKCairo > numerix : numpy # numpy, Numeric or numarray > interactive : True # see > http://matplotlib.sourceforge.net/interactive.html > verbose.level : debug-annoying # one of silent, helpful, debug, > debug-annoying > > Below is the output of the script I submitted when debug-annoying is > turned on: > In [3]: x = numpy.arange(1,100,1) > > In [4]: e1=-1.8 > > In [5]: e2=-2.1 > > In [6]: y = x**2 > > In [7]: z = x**-2 > > In [8]: f = figure(num=1) > > In [9]: f.clear() > > In [10]: ax = f.add_subplot(111) > > In [11]: p = ax.plot(x,y) > > In [12]: p1 = ax.plot(x,z) > > In [13]: title('This works -2.1 but this doesnot $-2.1$') > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > Out[13]: <matplotlib.text.Text instance at 0x8be1e8c> > > In [14]: legend((p[0],p1[0]),(r'$x^{%.2g}$'%(e1),r'$x^{%.2g}$'%(e2))) > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > Out[14]: <matplotlib.legend.Legend instance at 0x906f5ac> > > In [15]: draw() > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 > findfont returning > /usr/lib/python2.4/site-packages/matplotlib/mpl-data/fonts/ttf/Vera.ttf > > It looks like it is finding the fonts in 2.4 when I am using 2.5. I am > not sure how to change this behavior nor why that would be the only side > effect. > > Regards, > Brian > > > On Dec 5, 2007, at 1:36 PM, Michael Droettboom wrote: > >> It works for me on Linux with matplotlib 0.91.1, and Cairo 1.4.0. >> >> What version of matplotlib and Cairo are you using? It sounds like it >> may be pulling in the wrong fonts. Can you please send the contents >> of your matplotlibrc file, and also set "verbose.level" to >> "debug-annoying" and send the output? >> >> Cheers, >> Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA
On Dec 5, 2007 12:36 PM, Barry Wark <bar...@gm...> wrote: > Chris, > > I appologize for cryptic language and quickly written emails leading > you astray. I've included the diff of backend_cocoaagg.py (which has > also been sent to the mpl devs) which seems to work for me. I committed in r4571, presuming it is the same patch you sent before... JDH
Hello, I am using matplotlib svn 4626 and Cairo 1.4.0 all with python 2.5 with Ubuntu linux 7.10. The only lines in my matplotlibrc file which are uncommented are: backend : GTKCairo numerix : numpy # numpy, Numeric or numarray interactive : True # see http://matplotlib.sourceforge.net/interactive.html verbose.level : debug-annoying # one of silent, helpful, debug, debug-annoying Below is the output of the script I submitted when debug-annoying is turned on: In [3]: x = numpy.arange(1,100,1) In [4]: e1=-1.8 In [5]: e2=-2.1 In [6]: y = x**2 In [7]: z = x**-2 In [8]: f = figure(num=1) In [9]: f.clear() In [10]: ax = f.add_subplot(111) In [11]: p = ax.plot(x,y) In [12]: p1 = ax.plot(x,z) In [13]: title('This works -2.1 but this doesnot $-2.1$') findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf Out[13]: <matplotlib.text.Text instance at 0x8be1e8c> In [14]: legend((p[0],p1[0]),(r'$x^{%.2g}$'%(e1),r'$x^{%.2g}$'%(e2))) findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf Out[14]: <matplotlib.legend.Legend instance at 0x906f5ac> In [15]: draw() findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 12.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf findfont found Bitstream Vera Sans, normal, normal 400, normal, 14.0 findfont returning /usr/lib/python2.4/site-packages/matplotlib/mpl- data/fonts/ttf/Vera.ttf It looks like it is finding the fonts in 2.4 when I am using 2.5. I am not sure how to change this behavior nor why that would be the only side effect. Regards, Brian On Dec 5, 2007, at 1:36 PM, Michael Droettboom wrote: > It works for me on Linux with matplotlib 0.91.1, and Cairo 1.4.0. > > What version of matplotlib and Cairo are you using? It sounds like > it may be pulling in the wrong fonts. Can you please send the > contents of your matplotlibrc file, and also set "verbose.level" to > "debug-annoying" and send the output? > > Cheers, > Mike
On Dec 5, 2007 12:53 PM, Jonathan King <ki...@mi...> wrote: > i am having trouble installing matplotlib from source and thought i > would post my issue here. > i download matplotlib version 0.91.0 It looks possibly like a numpy problem (you have a pretty old version installed) > /usr/lib/python2.3/site-packages/numpy/core/include/numpy/ufuncobject.h:9: > error: 'intp' has not been declared Consider first upgrading to the latest numpy. JDH
i am having trouble installing matplotlib from source and thought i would post my issue here. i download matplotlib version 0.91.0 i am using a version of scientific linux, so i can't use rpm packages for some packages # uname -a Linux labcalx 2.6.23.8 #1 Fri Nov 23 10:54:41 EST 2007 i686 i686 i386 GNU/Linux i verified that i had the following packages installed via rpm: matplotlib core: zlib, zlib-devel, libpng, libpng-devel, freetype, freetype-devel, freetype-utils • gtk backend: gtk2-devel, gtk+-devel, pygtk2, glib-devel, pygtk2-devel, gnome-libs-devel, pygtk2-libglade • tk backend: tcl, tk, tkinter (and tk-devel) the wxpython package is not available on rpm for me (at least not that i can find) so i downloaded the source. that also seemed to compile and install fine. the libraries are in /usr/local/lib and that path is referenced in file /etc/ld.so.conf.d/wx.conf the ldconfig command seemed to find this okay and that looks like it should work. as per the user install guide, i downloaded setuptools-0.6c7-py2.3.egg without any trouble here is my output from the build command: # python setup.py build ============================================================================ BUILDING MATPLOTLIB matplotlib: 0.91.0 python: 2.3.4 (#1, Oct 9 2006, 18:22:22) [GCC 3.4.5 20051201 (Red Hat 3.4.5-2)] platform: linux2 REQUIRED DEPENDENCIES numpy: 0.9.8 freetype2: 9.7.3 OPTIONAL BACKEND DEPENDENCIES libpng: 1.2.7 Tkinter: Tkinter: 1.177, Tk: 8.4, Tcl: 8.4 wxPython: no * wxPython not found Gtk+: gtk+: 2.4.13, glib: 2.4.7, pygtk: 2.4.0, pygobject: [pre-pygobject] Qt: no Qt4: no Cairo: no OPTIONAL DATE/TIMEZONE DEPENDENCIES datetime: present, version unknown dateutil: matplotlib will provide pytz: matplotlib will provide OPTIONAL USETEX DEPENDENCIES dvipng: no ghostscript: 7.07 latex: 3.14159 pdftops: 3.00 EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES configobj: matplotlib will provide enthought.traits: matplotlib will provide [Edit setup.cfg to suppress the above messages] ============================================================================ running build running build_py copying lib/matplotlib/mpl-data/matplotlibrc -> build/lib.linux-i686-2.3/matplotlib/mpl-data copying lib/matplotlib/mpl-data/matplotlib.conf -> build/lib.linux-i686-2.3/matplotlib/mpl-data running build_ext building 'matplotlib.backends._backend_agg' extension g++4 options: '-fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -D_GNU_SOURCE -fPIC -fPIC' creating build/temp.linux-i686-2.3 creating build/temp.linux-i686-2.3/agg23 creating build/temp.linux-i686-2.3/agg23/src creating build/temp.linux-i686-2.3/src creating build/temp.linux-i686-2.3/CXX compile options: '-I/usr/lib/python2.3/site-packages/numpy/core/include -I/usr/include/libpng12 -I/usr/local/include -I/usr/include -I. -Isrc -Iswig -Iagg23/include -I. -I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I. -I/usr/include/python2.3 -c' g++4: src/_image.cpp In file included from /usr/include/python2.3/Python.h:8, from src/_image.cpp:7: /usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/c++/3.4.3/i386-redhat-linux/bits/os_defines.h:39, from /usr/include/c++/3.4.3/i386-redhat-linux/bits/c++config.h:35, from /usr/include/c++/3.4.3/iostream:44, from src/_image.cpp:1: /usr/include/features.h:150:1: warning: this is the location of the previous definition g++4: agg23/src/agg_rasterizer_scanline_aa.cpp g++4: CXX/IndirectPythonInterface.cxx In file included from /usr/include/python2.3/Python.h:8, from ./CXX/WrapPython.h:47, from ./CXX/IndirectPythonInterface.hxx:41, from CXX/IndirectPythonInterface.cxx:38: /usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/sys/time.h:22, from ./CXX/WrapPython.h:43, from ./CXX/IndirectPythonInterface.hxx:41, from CXX/IndirectPythonInterface.cxx:38: /usr/include/features.h:150:1: warning: this is the location of the previous definition g++4: src/backend_agg.cpp In file included from /usr/include/python2.3/Python.h:8, from ./CXX/WrapPython.h:47, from ./CXX/Extensions.hxx:48, from src/ft2font.h:18, from src/backend_agg.cpp:24: /usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/c++/3.4.3/i386-redhat-linux/bits/os_defines.h:39, from /usr/include/c++/3.4.3/i386-redhat-linux/bits/c++config.h:35, from /usr/include/c++/3.4.3/iostream:44, from src/backend_agg.cpp:4: /usr/include/features.h:150:1: warning: this is the location of the previous definition /usr/lib/python2.3/site-packages/numpy/core/include/numpy/ufuncobject.h:9: error: 'intp' has not been declared /usr/lib/python2.3/site-packages/numpy/core/include/numpy/ufuncobject.h:9: error: 'intp' has not been declared In file included from /usr/include/python2.3/Python.h:8, from ./CXX/WrapPython.h:47, from ./CXX/Extensions.hxx:48, from src/ft2font.h:18, from src/backend_agg.cpp:24: /usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/c++/3.4.3/i386-redhat-linux/bits/os_defines.h:39, from /usr/include/c++/3.4.3/i386-redhat-linux/bits/c++config.h:35, from /usr/include/c++/3.4.3/iostream:44, from src/backend_agg.cpp:4: /usr/include/features.h:150:1: warning: this is the location of the previous definition /usr/lib/python2.3/site-packages/numpy/core/include/numpy/ufuncobject.h:9: error: 'intp' has not been declared /usr/lib/python2.3/site-packages/numpy/core/include/numpy/ufuncobject.h:9: error: 'intp' has not been declared error: Command "g++4 -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -D_GNU_SOURCE -fPIC -fPIC -I/usr/lib/python2.3/site-packages/numpy/core/include -I/usr/include/libpng12 -I/usr/local/include -I/usr/include -I. -Isrc -Iswig -Iagg23/include -I. -I/usr/include/freetype2 -I/usr/local/include -I/usr/include -I. -I/usr/include/python2.3 -c src/backend_agg.cpp -o build/temp.linux-i686-2.3/src/backend_agg.o" failed with exit status 1 i tried different compilers (3.4.6 and 4.1.0), all of which failed with the same 'intp' has not been declared issue. i thought it was a problem with wx, so i edited setup.cfg to auto Gtk = True Gtkagg = True Tkagg = True Wxagg = False that cleared up the wx problem, but it _still_ won't compile. edited setup.cfg to a few different backends (gtk, gtkagg, tkagg) and they all fail. even setting the backend=Svg in the setup.cfg fails. any suggestions???? thanks!
hi, I think the new 0.91.1 has some kind of file handle leak at least when using python 2.4, tkagg, and within ipython. Using process explorer to look at filehandles opened by python then I get about 25 new open handles to vera.ttf per %run of the following script. from pylab import * figure(1) clf() title("jj") figure(2) clf() title("jj") However if I close("all") between %runs then all the open handles are closed. I tried the same thing with 0.90.1 and then I only get 2 handles for the same script and no increase on subsequent calls with or without close("all"). /Jörgen
Thanks for the background Barry. I was asking because I have a bit of image processing/analysis code (numpy/mpl/pil) that I would like to build a GUI front-end for. As I am a recent convert to the osx world, I thought it would be very slick to be able to do this with the xcode/IB tools. Since this is not high-priority work right now, I'll stick with wx for now. I will be interested to see how your Quartz backend comes along.
Barry Wark wrote: > We (at my work) are just starting to think about writing a more direct > Quartz backend for mpl. A native backend would let a matplotlib view > participate in newer Cocoa technologies, such as resolution > independence and CoreAnimation (it's possible with the current backend > method, but not quite as flexible). I'm curious what Cocoa and CoreAnimation might enable... If you are looking into writing a Quartz rendering backend, you may want to start with the matplotlib transforms branch (which should become the trunk shortly, once the 0.91 release bugs get shaken out.) The number of methods that a backend writer must provide has been greatly reduced on that branch. Cheers, Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA
On Dec 5, 2007 11:55 AM, Barry Wark <bar...@gm...> wrote: > Stephen, > > The CocoaAgg backend is not supported in IPython. Though we'd love to support it, were a few patches to land our way :) Cheers, f
Stephen, The CocoaAgg backend is not supported in IPython. You can use it in the non-interactive form (i.e. with a pylab.show() but you will have to close the window in order to return control to the IPython shell). It is possible to embed an MPL plot in a Cocoa application using the same trick as the CocoaAgg backend (rendering the plot using the Agg backend and then turning the rasterized bitmap into and NSBitmapImageRep and then displaying it in an NSImageView). I've posted previously about a py2app plugin which does just that and has an IB palette, but I haven't had time to update the IB palette to use the IB 3 plugin API yet. It uses Cocoa Bindings to provide data to the plot. I'm happy to send it to you as is, or you can wait until it's IB 3 ready. We (at my work) are just starting to think about writing a more direct Quartz backend for mpl. A native backend would let a matplotlib view participate in newer Cocoa technologies, such as resolution independence and CoreAnimation (it's possible with the current backend method, but not quite as flexible). This will make embedding easier, but will not solve the IPython issues. For now, one of the other backends, such as WXAgg or TkAgg is probably the better bet on OS X. barry On Dec 5, 2007, at 7:37 AM, Stephen Uhlhorn wrote: > I was just wondering what the status of the CocoaAgg backend is since > there is not much info available. > > Can it be used interactively w/ipython? > > Can it be used to embed mpl in a cocoa app and take advantage of all > the xcode/interface builder stuff in OS X? > > Thanks- > -stephen > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users@lists.s
Chris, I appologize for cryptic language and quickly written emails leading you astray. I've included the diff of backend_cocoaagg.py (which has also been sent to the mpl devs) which seems to work for me. Barry
It works for me on Linux with matplotlib 0.91.1, and Cairo 1.4.0. What version of matplotlib and Cairo are you using? It sounds like it may be pulling in the wrong fonts. Can you please send the contents of your matplotlibrc file, and also set "verbose.level" to "debug-annoying" and send the output? Cheers, Mike Brian Baughman wrote: > Hello all, > > I am trying to get a setup where I can have an interactive environment > and output to PDF files as needed. I currently have this setup > working in OS X 10.5 without problems. However, I cannot get a > similar setup working on linux. The best I have been able to do is by > using GTKCairo but it has a problem with rendering numbers in math > mode. Specifically when I put a number, say "-3.1415", into a string > the decimal is converted to a : and the "-" is turned into an "i". > Below is an example that gives this error: > import numpy > from pylab import * > x = numpy.arange(1,100,1) > e1=-1.8 > e2=-2.1 > y = x**2 > z = x**-2 > f = figure(num=1) > f.clear() > ax = f.add_subplot(111) > p = ax.plot(x,y) > p1 = ax.plot(x,z) > title('This works -2.1 but this doesnot $-2.1$') > legend((p[0],p1[0]),(r'$x^{%.2g}$'%(e1),r'$x^{%.2g}$'%(e2))) > draw() > savefig('test.pdf') > > The output looks fine in GTKAgg but then I get an error on glib. > > Anyone have any ideas on how to get it working? > > Regards, > Brian > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA
At 10:03 AM -0800 2007年12月05日, Christopher Barker wrote: >Russell E Owen wrote: >>At 10:08 AM -0500 2007年12月05日, Stephen Uhlhorn wrote: >>>Just for my edification, why can't the egg version be linked >>>against/include a different Tcl/Tk? >> >>If you mean why can't it be built that way in the first place, I >>don't know. The guy who builds it apparently doesn't read this list, > >Sure he does (if you mean the matplotlib list), and he did ask about >it right before this release. Maybe that was asked on >matplotlib-devel though (I filter them to the same place). It was on matploblib-devel. I'll start skimming that newsgroup. >>I suspect the official egg can somehow be patched, but I find it >>easier to just build my own and put that on pythonmac. > >Ideally, there would be only one binary version, and it would work >with either Tcl/Tk. Is that possible? or is this like the old wx >situation, where it can only be run with the same version it is >built against. Arrggg! I hope not. The version I build *can* be used with the built in Tcl/Tk. The version Charlie Moad builds cannot be used with TkAgg and a 3rd party Tcl/Tk -- it not only won't use the library, but it also acts flaky. Older versions crashed. 0.91.1 doesn't crash, but import of pylab fails with a traceback. For some reason it seems to be necessary to have a 3rd party Tcl/Tk installed when building matplotlib. It seems a shame. Tkinter in Python 2.4 was the same way, but that got fixed in Python 2.5 (I don't whether the installer got fixed or whether whoever builds Mac Python 2.5 installed a 3rd party Tcl/Tk). >If there really do need to be two, then they should be labeled >somehow, and both be up on python mac. Since there don't need to be two versions this is not necessary. However, Charlie Moad appears to be willing to start building a version that works with 3rd party Tcl/Tk. I really hope that happens. -- Russell
Hello all, I am trying to get a setup where I can have an interactive environment and output to PDF files as needed. I currently have this setup working in OS X 10.5 without problems. However, I cannot get a similar setup working on linux. The best I have been able to do is by using GTKCairo but it has a problem with rendering numbers in math mode. Specifically when I put a number, say "-3.1415", into a string the decimal is converted to a : and the "-" is turned into an "i". Below is an example that gives this error: import numpy from pylab import * x = numpy.arange(1,100,1) e1=-1.8 e2=-2.1 y = x**2 z = x**-2 f = figure(num=1) f.clear() ax = f.add_subplot(111) p = ax.plot(x,y) p1 = ax.plot(x,z) title('This works -2.1 but this doesnot $-2.1$') legend((p[0],p1[0]),(r'$x^{%.2g}$'%(e1),r'$x^{%.2g}$'%(e2))) draw() savefig('test.pdf') The output looks fine in GTKAgg but then I get an error on glib. Anyone have any ideas on how to get it working? Regards, Brian
Russell E Owen wrote: > At 10:08 AM -0500 2007年12月05日, Stephen Uhlhorn wrote: >> Just for my edification, why can't the egg version be linked >> against/include a different Tcl/Tk? > > If you mean why can't it be built that way in the first place, I > don't know. The guy who builds it apparently doesn't read this list, Sure he does (if you mean the matplotlib list), and he did ask about it right before this release. Maybe that was asked on matplotlib-devel though (I filter them to the same place). > I suspect the official egg can somehow be patched, but I find it > easier to just build my own and put that on pythonmac. Ideally, there would be only one binary version, and it would work with either Tcl/Tk. Is that possible? or is this like the old wx situation, where it can only be run with the same version it is built against. Arrggg! I hope not. If there really do need to be two, then they should be labeled somehow, and both be up on python mac. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no...
I primarily follow the dev list, but you've caught my eye. ;) So to be clear, you would just like me to install some other tcl/tk before I do the "official" matplotlib osx binaries. What package should I be installing and where should I get it from. As long as it still works with the bundled tck/tk I would have no problems doing this. Thanks, - Charlie On Dec 5, 2007 12:01 PM, Russell E Owen <ro...@ce...> wrote: > At 10:08 AM -0500 2007年12月05日, Stephen Uhlhorn wrote: > >On Dec 4, 2007 5:14 PM, Russell E. Owen <ro...@ce...> wrote: > > > >> If you use Tcl/Tk and use a current version (instead of the ancient > >> version that is built in) then use the packages at pythonmac. I just > >> built 0.91.1 today and it should show up there soon. Meanwhile you can > >> get it from here: > >> <http://www.astro.washington.edu/rowen/pythoninstallers/> > >> > >> I hope that someday the official Mac egg version will work with 3rd > >> party Tcl/Tk but no version I've tried has -- including 0.91.1. > > > >Does this mean that the only difference between the egg and pythonmac > >version is how it's linked against Tcl/Tk? > > I suspect you are right. But I only build the pythonmac version, not > the official version, so I don't know for sure. I build my version > using: > <http://www.astro.washington.edu/rowen/BuildingMatplotlibForMac.html>. > I don't do anything special, but I do have a 3rd party Tcl/Tk > installed before I build and that seems to make all the difference. > > >Just for my edification, why can't the egg version be linked > >against/include a different Tcl/Tk? > > If you mean why can't it be built that way in the first place, I > don't know. The guy who builds it apparently doesn't read this list, > and I understand he's on some mailing list that I don't subscribe to. > > I suspect the official egg can somehow be patched, but I find it > easier to just build my own and put that on pythonmac. > > -- Russell > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
John Hunter wrote: > You cannot import pylab and use the FigureCanvasWx at the same time. > Please follow the lead of examples/embedding_in_wx*.py if you want to > use matplotlib in a wxpython GUI. or use wxmpl: http://agni.phys.iit.edu/~kmcivor/wxmpl/ By the way, couldn't that be distributed with Matplotlib? Maybe in toolkits, if not the main distro. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no...
I feel we're getting a tad bit off topic from my original inquiry. Does anyone have an answer for me? Thanks. On Dec 5, 2007 8:42 AM, massimo sandal <mas...@un...> wrote: > rex ha scritto: > > massimo sandal <mas...@un...> [2007年12月04日 09:18]: > >> On a related note, I *hate* that hitting "reply" uses the mail address > >> of the parent poster, instead than that of the mailing list. The scipy > >> and the gentoo mailing list (two other examples I know) behave more > >> properly. Is this a sourceforge quirk? > > > > The list follows RFC 2822. The Reply-To header is intended to be > > created by the originator of the message. List software that > > overwrites the Reply-To header destroys the function it's intended > > for. > > > > There's an excellent essay on this at: > > > > http://woozle.org/~neale/papers/reply-to-still-harmful<http://woozle.org/%7Eneale/papers/reply-to-still-harmful> > > > > Mailman implements RFC 2369, which is intended to address this > > issue. If you want replies to go to the list, I suggest that you > > use a mail client that follows RFC 2369. If you choose to use old > > software that doesn't recognize the List-Post header, please don't > > complain about software that follows RFC standards. > > Thanks for the article. I read it, and I must say I disagree. This is > the tricky part: > > "Your list software is not "the author of the message", so it must not > set or in any way meddle with the Reply-To header. " > > That's what I think is wrong. When interacting with a mailing list, I > assume I'm not interacting just with you or others. I'm receiving mails > *from the ML* and sending mails *to the ML*. Not receiving mails from > Alice and sending mails to Bob. > > In other words: A ML, in my experience, is not different from a public > forum. When I hit "reply" on a forum, the post goes on the forum, not on > the mailbox of the previous poster. > > I'm all for standards and for consistent behaviour and I understand the > logic behind that article; what the authors of the RFC got wrong, in my > opinion, it considering a mailing list just as a gigantic CC: by > disconnected people instead than of a forum-like object. The fact both > use the mail protocol doesn't change the fact they're different objects. > > But of course that's only a philosophical problem. Thanks to the article > I also discovered that "reply to all" sends mail both to the ML and the > original sender (Never bothered to try, my fault). Although I find it a > little funny. > > m. > > -- > Massimo Sandal > University of Bologna > Department of Biochemistry "G.Moruzzi" > > snail mail: > Via Irnerio 48, 40126 Bologna, Italy > > email: > mas...@un... > > tel: +39-051-2094388 > fax: +39-051-2094387 > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > >
At 10:08 AM -0500 2007年12月05日, Stephen Uhlhorn wrote: >On Dec 4, 2007 5:14 PM, Russell E. Owen <ro...@ce...> wrote: > >> If you use Tcl/Tk and use a current version (instead of the ancient >> version that is built in) then use the packages at pythonmac. I just >> built 0.91.1 today and it should show up there soon. Meanwhile you can >> get it from here: >> <http://www.astro.washington.edu/rowen/pythoninstallers/> >> >> I hope that someday the official Mac egg version will work with 3rd >> party Tcl/Tk but no version I've tried has -- including 0.91.1. > >Does this mean that the only difference between the egg and pythonmac >version is how it's linked against Tcl/Tk? I suspect you are right. But I only build the pythonmac version, not the official version, so I don't know for sure. I build my version using: <http://www.astro.washington.edu/rowen/BuildingMatplotlibForMac.html>. I don't do anything special, but I do have a 3rd party Tcl/Tk installed before I build and that seems to make all the difference. >Just for my edification, why can't the egg version be linked >against/include a different Tcl/Tk? If you mean why can't it be built that way in the first place, I don't know. The guy who builds it apparently doesn't read this list, and I understand he's on some mailing list that I don't subscribe to. I suspect the official egg can somehow be patched, but I find it easier to just build my own and put that on pythonmac. -- Russell