>> Windows debug extensions have a suffix, d. If you don't install the
>> debug version of numpy, you can't use it with debug Python.
*red face* forgot about --debug...
> Yes, this has actually nothing to do with python 2.6. I noticed the
> crash, thought naively it would be easy to fix, but
> Windows debug extensions have a suffix, d. If you don't install the
> debug version of numpy, you can't use it with debug Python.
Ah, thank you. Sorry for the newb question: how do you install the
debug version (for msvc)?
___
Numpy-discussion mailing
2009/3/3 James Watson :
>> I would appreciate if people would test building numpy
>> (trunk); in particular since some issues are moderately complex and
>> system dependent
>
> On Vista with VS2008, numpy rev r6535, I get the following behaviour:
> 1. Building and installing numpy on python 2.6.1 c
Hi James,
James Watson wrote:
>> I would appreciate if people would test building numpy
>> (trunk); in particular since some issues are moderately complex and
>> system dependent
>>
>
> On Vista with VS2008, numpy rev r6535, I get the following behaviour:
> 1. Building and installing numpy on
> I would appreciate if people would test building numpy
> (trunk); in particular since some issues are moderately complex and
> system dependent
On Vista with VS2008, numpy rev r6535, I get the following behaviour:
1. Building and installing numpy on python 2.6.1 compiled in debug
mode succeeds,
Hi,
this is really good news, thanks for working on this. I'm looking
forward to switching from 2.4 to 2.6 at work but we really need numpy
and matplotlib.
I have successfully built numpy on windows using mingw.
Some basic tests at the interactive prompt suggests it works.
/Jörgen
David Cou
Hi,
I think I finally solve most serious issues for numpy on python 2.6
on windows. I would appreciate if people would test building numpy
(trunk); in particular since some issues are moderately complex and
system dependent, I am interested in the following configurations:
- python install
