It works! Thanks for such quick turnaround!
If I may add a suggestion for the matplotlib setup from sources
(which I had tried just after the egg install failed):
The directory specified to the --prefix argument of setup.py would
seem like a natural addition to basedir in setupext.py (of cour
I have replaced the binary with a working version.
Thanks again for the catch,
Charlie
On Jan 11, 2008 2:15 PM, Charlie Moad <[EMAIL PROTECTED]> wrote:
> Apparently a dynamic link snuck into the build. Typically everything
> is statically included. You can see this by running the following
Apparently a dynamic link snuck into the build. Typically everything
is statically included. You can see this by running the following
command:
uaternion:matplotlib cmoad$ otool -L ft2font.so
ft2font.so:
/usr/local/lib/libfreetype.6.dylib (compatibility version 10.0.0,
current version 10
Hello all,
after installing matplotlib 0.91.2 from the sourceforge egg on OS X
10.4.11 (Python 2.5.1), I get the following error:
>>> import pylab
Traceback (most recent call last):
File "", line 1, in
File "/Users/vallis/lib/python2.5/site-packages/matplotlib-0.91.2-
py2.5-macosx-10.3
Hi Thorsten,
On Wednesday 09 January 2008 15:35, Thorsten Kranz wrote:
> Hi list, Hi Matthias,
>
> I found another way to deal with this problem. when defining the colorbar,
> one can give an additional kwarg "format", so by defining the kwarg
> "format=formatter", we solved the problem.
I'm happ
Hello Mike,
Hello list,
On Wednesday 09 January 2008 18:21, Michael Droettboom wrote:
> Thanks for the patch. However, perhaps a more general solution would be
> to use the Python locale module to format numbers according to different
> locales.
I agree with you, but it seems to be hard to do.
Replying to myself...
Erik Cederstrand wrote:
> Hi!
>
> I'm trying to make a clickable plot_date() plot (using the Pylons
> framework). What I need is the pixel coordinates of the data points I
> give to plot_date(), but the trans.seq_x_y() function doesn't like
> Datetime:
>
>>> xcoords
Now this is a totally shot in the dark, but I remember similar
'features' from good old unix times, where the X display was palette
instead of true-color, and you'd start some other app that forced its
own colors to the X display, thus changing the palette of other windows.
No idea though why it wo