I have a problem with backend: by default it was Agg; i tried to change the
file .matplotlibrc and to put GTKAgg, but as I import pylab I got these
errors:
from pylab import *
Traceback (most recent call last):
File stdin, line 1, in ?
File /usr/local/lib/python2.4/site-packages/pylab.py,
Chiara Caronna wrote:
I have a problem with backend: by default it was Agg; i tried to change the
file .matplotlibrc and to put GTKAgg, but as I import pylab I got these
errors:
File
/usr/local/lib/python2.4/site-packages/matplotlib/backends/backend_gtk.py,
line 6, in ?
import
On Wednesday 21 February 2007 2:45:25 am Eric Firing wrote:
Matthew Auger wrote:
Ah...right. That works well enough (I believe that I originally had
editted backend_bases to circumvent the format_coord call--clearly not
the best solution)! I don't know of a good reason to *not* use the axis
At 9:42 AM -0800 2007-02-21, Chris Barker wrote:
Russell E Owen wrote:
I did earlier today; I'm hoping it will go up in the next day or so.
WXAgg is built against wxPython 2.6.x because last I heard the
2.8.x issues weren't resolved.
Correct. I'm still not sure how well MPL works with
Chris Barker wrote:
Russell E Owen wrote:
I did earlier today; I'm hoping it will go up in the next day or so.
WXAgg is built against wxPython 2.6.x because last I heard the 2.8.x
issues weren't resolved.
Correct. I'm still not sure how well MPL works with wxPython2.8 on other
Okay, I tried saving using the postscript format, and I end up with the ugly
plot also. In fact, if I maximize the plot and then save as .ps file, I get
ugly plot as well. So, saving it in PS made no difference - that part is
correct but it means I end up with the same font, and dimension
Werner F. Bruhin wrote:
If someone can do a Windows build against a wxPython 2.8 version (and
Python 2.5) I could do some testing.
Is there a list of what the problems are?
no.
One is that it won't build, due to a code error in the extension -- I
don't know why that same error didn't
Hi,
I would like to add another annoying aspect of the digits in the GUI:
When a log axis is used the displayed numbers looks like 10^-8.23
which is definitely not human readable.
Do somebody know a quick fix to obtain something like 5.89e-9 or 5.89x10^-9 ?
Thanks,
David
Okay, I posted the ugly vs pretty plots at:
http://new.photos.yahoo.com/kimwaic106/album
I stripped out most of the titles and subtitles but I think you can still see
the difference between the two. (Don't worry about the middle unintelligble
part).
Regards,
--
John Henry
- Original
On Feb 21, 2007, at 1:58 PM, Christopher Barker wrote:
Werner F. Bruhin wrote:
Is there a list of what the problems are?
One is that it won't build, due to a code error in the extension -- I
don't know why that same error didn't cause a problem with earlier
versions of wxPython.
The WXAgg
On Wednesday 21 February 2007 03:44:56 pm [EMAIL PROTECTED]
wrote:
Okay, I posted the ugly vs pretty plots at:
http://new.photos.yahoo.com/kimwaic106/album
I stripped out most of the titles and subtitles but I think you can still
see the difference between the two. (Don't worry about the
Darren Dale wrote:
I dont really see any difference between these two plots, aside from the
obvious and expected difference in font size and line width.
I suspect that is the OP's issue. Maybe this will help:
http://www.scipy.org/Cookbook/Matplotlib/AdjustingImageSize
-Chris
--
Russell and Eric, many thanks for sticking with me on this issue. I've
been able to reproduce the problem just by calling gc.collect() without
loading Matplotlib, so it looks like the problem is elsewhere. I'm very
sorry I didn't realize this sooner.
Cheers,
Anand
FYI: matplotlib 0.90.0 for Python 2.5 is now available at
http://pythonmac.org/packages. I did not build a version for Python
2.4.
Thanks, downloading as I type.
-
Take Surveys. Earn Cash. Influence the Future of IT
14 matches
Mail list logo
