I had this problem too, on Leopard. Trying to easy_install the egg
named as downloaded from sourceforge results in stuff being downloaded
and failing to build.
Renaming the egg as suggested by Vincent results in an 'easy install'.
-
Andrew Charles
Centre for Australian Wea
I recently removed my existing numpy and matplotlib installations and
rebuilt from svn, then installed the matplotlib-0.98.0 egg
If I fire up ipython and then get to work everything is ok, but
attempting to start ipython with the -pylab flag results in a numpy
version error message, as shown below.
Hi all,
I have just upgraded to 0.93.1 (actually it turned out I did not even have
to remove the 0.90 egg, python imports from 0.91 all by itself. I do not
completely understand why, but that was a nice surprise...) and now the
mixing of normal text and mathtext works nicely.
Is it possible to
Hi Andrew,
It looks like you have an old version of numpy somewhere on your python path.
You need to delete all the old numpy installs/eggs from site-packages, and
anywhere else on your PYTHONPATH.
On Friday 06 June 2008 3:48:05 am Andrew Charles wrote:
> I recently removed my existing numpy a
The choice for math fonts is somewhat limited, because so few fonts have
the necessary symbols and spacing information, even if they are
reasonably complete Unicode-wise.
You basically have three supported choices, and one experimental choice,
set with the mathtext.fontset parameter:
cm: T
I just used the default 10.5 compiler. I didn't use -Os for the whole
run though. I would just copy the gcc command on the files where it
failed and replace -O3 with -Os. Kind of lame, I know, but most the
build I did was ran with -O3.
- Charlie
On Thu, Jun 5, 2008 at 8:19 PM, Christopher Bark
So I'll admit that I renamed that file to -fat manually. The reason I
did this is because it gets named -i386 by default even though it is a
fat build. Does anyone have a good idea of how to fix this?
- Charlie
On Fri, Jun 6, 2008 at 3:07 AM, Andrew Charles <[EMAIL PROTECTED]> wrote:
> I had th
I'm sure that would work, but John's make target 'build_osx105' is
much easier, particularly for end users.
$ make build_osx105
That's it. Unpythonic in it's appearance, but sets the required
CFLAGS and calls setup.py.
On Fri, Jun 6, 2008 at 7:41 AM, Charlie Moad <[EMAIL PROTECTED]> wrote:
> I
On Fri, Jun 6, 2008 at 11:16 AM, Christopher Burns <[EMAIL PROTECTED]> wrote:
> I'm sure that would work, but John's make target 'build_osx105' is
> much easier, particularly for end users.
>
> $ make build_osx105
>
> That's it. Unpythonic in it's appearance, but sets the required
> CFLAGS and cal
