[SciPy-user] building 64bit scipy
Mon Apr 20 13:53:53 CDT 2009
On Mon, Apr 20, 2009 at 13:45, Dan Yamins <firstname.lastname@example.org> wrote:
> On Mon, Apr 20, 2009 at 1:31 PM, Robert Kern <email@example.com> wrote:
>> On Mon, Apr 20, 2009 at 12:28, Dan Yamins <firstname.lastname@example.org> wrote:
>> > Great, that explains everything, thanks very much for all your help. I
>> > guess I'd have to learn distutils, and then numpy.distutils before I
>> > understood how to write such commands myself.
>> > BTW, scipy.test('full') showed an error when run on 64bit python. I've
>> > included below the results from the test, first for 64 bit and then for
>> > comparison for the 32 bit, where no unknown failure showed. (don't feel
>> > compelled to look into this if you don't have time/interest, the error
>> > is
>> > unlikely to affect any of the work I do, so I don't really much care to
>> > fix
>> > it right now)
>> It looks like you have incompatible versions of numpy and scipy. What
>> versions are you trying to install together?
> Well, I've installed numpy 1.3.0 (from downloading the most recent stable
> source release from numpy's sourceforge page).
> Then I installed scipy 0.7.0 (downloading again the most recent stable
> source release from scipy's sourceforge page)
> I installed both first using python 2.5.4 (using the most recent OSX binary
> from www.python.org -- this is a 32bit binary) and then also on python
> 2.6.2 that I build as a 64-bit binary using macports.
> Are you saying that the installation both for both versions of python are
> bad? Or just the 64bit one?
Sorry, I was just referring to the 32 bit one. I really doubt that you
have a clean install of scipy 0.7.0; the "set_package_path" stuff was
removed before the 0.7.0 release.
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco
More information about the SciPy-user