Hi,
The problem will arise for every package, not only numpy, so Apple fixing
this is the best solution IMHO.
Matthieu
2007/11/1, Brian Granger [EMAIL PROTECTED]:
Hi,
It turns out that Leopard includes numpy. But it is an older version
that won't detect the version string of gfortran
Matthieu Brucher wrote:
Hi,
The problem will arise for every package, not only numpy, so Apple
fixing this is the best solution IMHO.
It's unlikely they are going to. If they put that stuff there, it's because they
are using it for something, not as an (in)convenience to you. I don't
It's unlikely they are going to. If they put that stuff there, it's because
they
are using it for something, not as an (in)convenience to you. I don't
recommend
using the Python.framework in /System for anything except for distributing
lightweight .apps. In that case, you can control your
More evidence that just using the python.org python binary isn't a
universal fix for everyone:
From a thread on one of the python-dev lists:
Which reminds me -- what version of Python is in Leopard?
2.5.1 + most of the patches that will be in 2.5.2 + some additional
patches by Apple. AFAIK the
Robert Kern wrote:
The problem will arise for every package, not only numpy, so Apple
fixing this is the best solution IMHO.
It's unlikely they are going to. If they put that stuff there, it's because
they
are using it for something, not as an (in)convenience to you. I don't
recommend
In article [EMAIL PROTECTED],
Christopher Barker [EMAIL PROTECTED] wrote:
[...] AARRGG!
[...]
Hence Roberts solution: treat the Apple Python as a system only tool,
only to be added to by Apple themselves. I guess that's OK, but it's
really silly that it has to be that way.
The solution:
