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
I ran into this problem a year or so ago. I suspect my messages to the list are
in the archives somewhere. It is a known problem and involves a hard-coded
maximum number of iterations in the SVD code. The problem is on the LaPack
side. You can go in and change it, but then you have to recompil
On Mon, Feb 2, 2009 at 18:21, wrote:
> Hello list.. I've run into two SVD errors over the last few days. Both
> errors are identical in numpy/scipy.
>
> I've submitted a ticket for the 1st problem (numpy ticket #990). Summary
> is: some builds of the lapack_lite module linking against system LAPA
Hello list.. I've run into two SVD errors over the last few days. Both
errors are identical in numpy/scipy.
I've submitted a ticket for the 1st problem (numpy ticket #990). Summary
is: some builds of the lapack_lite module linking against system LAPACK
(not the bundled dlapack_lite.o, etc) give a
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
Nils Wagner wrote:
> On Mon, 02 Feb 2009 14:07:35 -0600
> Ryan May wrote:
>> Nils Wagner wrote:
> Is this a 64-bit problem ?
>
I don't know if it's a 64-bit problem per-se, so much as
a disagreement between
fortran and numpy. Numpy is making the size of the
integer
On Mon, 02 Feb 2009 14:07:35 -0600
Ryan May wrote:
> Nils Wagner wrote:
Is this a 64-bit problem ?
>>> I don't know if it's a 64-bit problem per-se, so much as
>>> a disagreement between
>>> fortran and numpy. Numpy is making the size of the
>>> integer fields 8 bytes, while
>>> in
Nils Wagner wrote:
>>> Is this a 64-bit problem ?
>>>
>> I don't know if it's a 64-bit problem per-se, so much as
>> a disagreement between
>> fortran and numpy. Numpy is making the size of the
>> integer fields 8 bytes, while
>> in Fortran, they're only 4 bytes. When constructing
>> your dtyp
On Mon, 02 Feb 2009 13:38:14 -0600
Ryan May wrote:
> Nils Wagner wrote:
>> On Mon, 02 Feb 2009 10:17:13 -0600
>> Ryan May wrote:
>>> Every write statement in fortran first writes out the
>>> number of bytes that will
>>> follow, *then* the actual data. So, for instance, the
>>> first write
Nils Wagner wrote:
> On Mon, 02 Feb 2009 10:17:13 -0600
> Ryan May wrote:
>> Every write statement in fortran first writes out the
>> number of bytes that will
>> follow, *then* the actual data. So, for instance, the
>> first write to file in
>> your program will write the bytes corresponding
On Mon, 02 Feb 2009 10:17:13 -0600
Ryan May wrote:
> Nils Wagner wrote:
>> On Mon, 2 Feb 2009 13:39:32 +0100
>> Matthieu Brucher wrote:
>>> Hi,
>>>
>>> There was a discussion about this last week. You can
>>>find it int he
>>> archives ;)
>>>
>>> Matthieu
>>
>> Hi Matthieu,
>>
>> Sorry but
On Tue, Feb 3, 2009 at 2:23 AM, Hanni Ali wrote:
> Hi David,
>
> I used free trials of the Intel and PGI compilers to try to compile an
> external BLAS/LAPACK in conjunction with VS 2008. I also had no problems
> getting the C code to compile, but couldn't get linking to work succesfully
> with fo
Hi David,
I used free trials of the Intel and PGI compilers to try to compile an
external BLAS/LAPACK in conjunction with VS 2008. I also had no problems
getting the C code to compile, but couldn't get linking to work succesfully
with fortran stuff. I would not be surprised if we could get a licen
Nils Wagner wrote:
> On Mon, 2 Feb 2009 13:39:32 +0100
> Matthieu Brucher wrote:
>> Hi,
>>
>> There was a discussion about this last week. You can find it int he
>> archives ;)
>>
>> Matthieu
>
> Hi Matthieu,
>
> Sorry but I missed that.
> Anyway I have some trouble with my short example.
>
>
On Tue, Feb 3, 2009 at 12:28 AM, Mike Colonno wrote:
> Hi folks ~
>
>
>
> Any thoughts on the below?
It is hard to say, but I suspect a problem in your BLAS/LAPACK because
it fails on importing lapack_lite. Your error message is so generic
that it does not give any useful
Hi folks ~
Any thoughts on the below? I n searching the web I found some other
references to " ImportError: DLL load failed: Invalid access to memory
location" but none specific to Numpy. As an aside: will there be a Windows x64
binary distributed with the next release o
On Mon, 2 Feb 2009 13:39:32 +0100
Matthieu Brucher wrote:
Hi,
There was a discussion about this last week. You can
find it int he archives ;)
Matthieu
Hi Matthieu,
Sorry but I missed that.
Anyway I have some trouble with my short example.
g77 -c binary_fortran.f
g77 -o io binary_fortra
Hi,
There was a discussion about this last week. You can find it int he archives ;)
Matthieu
2009/2/2 Nils Wagner :
> Hi all,
>
> How can I import FORTRAN binary files using numpy ?
>
> In FORTRAN I can do
>
> OPEN(10,FILE='test.mat',FORM='unformatted')
>
> 100 CONTINUE
> READ(10
Hi all,
How can I import FORTRAN binary files using numpy ?
In FORTRAN I can do
OPEN(10,FILE='test.mat',FORM='unformatted')
100 CONTINUE
READ(10,END=999) IROW, ICOL, VALUE
GOTO 100
999 CONTINUE
END
And In Python/numpy ?
Any pointer would be apprecia
23 matches
Mail list logo
