Subject: Re: [Numpy-discussion] f2py: VS version on Windows
On Tue, Feb 3, 2009 at 10:55 AM, Sturla Molden wrote:
>
>> Python extensions must be built using the same compiler as was used to
>> build the Python binary. Python 2.5.4 was built using MSVC2003 and so
>> extensions
On Tue, Feb 3, 2009 at 10:55 AM, Sturla Molden wrote:
>
>> Python extensions must be built using the same compiler as was used to
>> build the Python binary. Python 2.5.4 was built using MSVC2003 and so
>> extensions for it must be built using the same compiler. The exception
>> to this rule is t
You learn something new every day. It turns out I had previously been
given wrong information and I apologize for passing that along to the
list.
-Patrick
On Mon, Feb 2, 2009 at 8:03 PM, Sturla Molden wrote:
>
>> I'm trying to test out f2py in Windows (python 2.5.4 32-bit
>> for n
> I'm trying to test out f2py in Windows (python 2.5.4 32-bit
> for now + most recent Numpy). I'd like to use the Intel
> compilers, but msvc is fine if needed. I get the output below
> about which I have a question re: the warning about VS
> version. I have VS 2008 currently which sho
> Python extensions must be built using the same compiler as was used to
> build the Python binary. Python 2.5.4 was built using MSVC2003 and so
> extensions for it must be built using the same compiler. The exception
> to this rule is that extensions built using mingw32 (and msys) will
> work wi
Hi Mike,
Python extensions must be built using the same compiler as was used to
build the Python binary. Python 2.5.4 was built using MSVC2003 and so
extensions for it must be built using the same compiler. The exception
to this rule is that extensions built using mingw32 (and msys) will
work wit
I'm trying to test out f2py in Windows (python 2.5.4 32-bit for now
+ most recent Numpy). I'd like to use the Intel compilers, but msvc is fine if
needed. I get the output below about which I have a question re: the warning
about VS version. I have VS 2008 currently which should have
