>> 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,
David Cournapeau wrote:
> Lenard Lindstrom wrote:
>
>> Sorry for the confusion. I meant that I don't like patching SDL and
>> such. I build these in msys using the "configure; make install"
>> incantation, so can't easily use magic like manifest files.
>>
>
> I don't know about SDL :) num
Lenard Lindstrom wrote:
> Sorry for the confusion. I meant that I don't like patching SDL and
> such. I build these in msys using the "configure; make install"
> incantation, so can't easily use magic like manifest files.
I don't know about SDL :) numpy needs manifests at the configuration
stage
David Cournapeau wrote:
> Lenard Lindstrom wrote:
>
>> David Cournapeau wrote:
>>
>>
>>>
>>> Do you mean on xp 32 bits or 64 bits ? For the later, I have yet to
>>> submit patchs to the mingw-w64 project - the whole libmsvcr90.a is
>>> missing, actually. For 32 bits, I simply got around
Lenard Lindstrom wrote:
> David Cournapeau wrote:
>
>> Do you mean on xp 32 bits or 64 bits ? For the later, I have yet to
>> submit patchs to the mingw-w64 project - the whole libmsvcr90.a is
>> missing, actually. For 32 bits, I simply got around it by changing the
>> missing functions in numpy
Lenard Lindstrom wrote:
> David Cournapeau wrote:
>
>> Lenard Lindstrom wrote:
>>
>>
>>> David Cournapeau wrote:
>>>
>>>
Hi Lenard,
On Sun, Dec 28, 2008 at 5:05 AM, Lenard Lindstrom wrote:
> Hi everyone,
>
>
David Cournapeau wrote:
> Lenard Lindstrom wrote:
>
>> David Cournapeau wrote:
>>
>>> Hi Lenard,
>>>
>>>
>>> On Sun, Dec 28, 2008 at 5:05 AM, Lenard Lindstrom wrote:
>>>
>>>
Hi everyone,
[snip]
I am willing to offer what advice
I can to get NumPy
David Cournapeau wrote:
> Hi Lenard,
>
>
> On Sun, Dec 28, 2008 at 5:05 AM, Lenard Lindstrom wrote:
>
>> Hi everyone,
>>
>> I build the Pygame dependencies for Windows. With the next Pygame
>> release, 1.9.0, we would like to include Python 2.6 support. As you
>> already know, Pygame has NumPy
Lenard Lindstrom wrote:
> David Cournapeau wrote:
>> Hi Lenard,
>>
>>
>> On Sun, Dec 28, 2008 at 5:05 AM, Lenard Lindstrom wrote:
>>
>>> Hi everyone,
>>>
>>> I build the Pygame dependencies for Windows. With the next Pygame
>>> release, 1.9.0, we would like to include Python 2.6 support. As you
David Cournapeau wrote:
> Hi Lenard,
>
>
> On Sun, Dec 28, 2008 at 5:05 AM, Lenard Lindstrom wrote:
>
>> Hi everyone,
>>
>> I build the Pygame dependencies for Windows. With the next Pygame
>> release, 1.9.0, we would like to include Python 2.6 support. As you
>> already know, Pygame has NumPy
Hi Lenard,
On Sun, Dec 28, 2008 at 5:05 AM, Lenard Lindstrom wrote:
> Hi everyone,
>
> I build the Pygame dependencies for Windows. With the next Pygame
> release, 1.9.0, we would like to include Python 2.6 support. As you
> already know, Pygame has NumPy bindings. Though NumPy is not required,
On Sat, Dec 27, 2008 at 15:05, Lenard Lindstrom wrote:
> Hi everyone,
>
> I build the Pygame dependencies for Windows. With the next Pygame
> release, 1.9.0, we would like to include Python 2.6 support. As you
> already know, Pygame has NumPy bindings. Though NumPy is not required,
> it is a usefu
Hi everyone,
I build the Pygame dependencies for Windows. With the next Pygame
release, 1.9.0, we would like to include Python 2.6 support. As you
already know, Pygame has NumPy bindings. Though NumPy is not required,
it is a useful addition. I understand NumPy is built with MinGW on
Windows,
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
19 matches
Mail list logo