Mathew Yeates wrote:
> I finally got things linked with libg2c but now I get
> import linalg -> failed: ld.so.1: python: fatal: relocation error: file
> /u/fuego0/myeates/lib/python2.4/site-packages/numpy/linalg/lapack_lite.so:
> symbol dgeev_: referenced symbol not found
>
> I looked all throug
I finally got things linked with libg2c but now I get
import linalg -> failed: ld.so.1: python: fatal: relocation error: file
/u/fuego0/myeates/lib/python2.4/site-packages/numpy/linalg/lapack_lite.so:
symbol dgeev_: referenced symbol not found
I looked all through my ATLAS source and I see no dg
I've updated the description of the array interface (array protocol).
The web-page is
http://numeric.scipy.org/array_interface.html
Basically, the Python-side interface has been compressed to the single
attribute __array_interface__. There is still the __array_struct__
attribute which now h
Heres the problem The function get_flags_linker_so in
numpy/distutils/fcompiler/gnu.py is not called anywhere. Because of
this, g2c is not added as a library and -mimpure-text is not set. This
causes the "s_wsfe unresolved" problem.
Anybody know how to fix this?
Mathew
___
Francesc Altet wrote:
>A Dimarts 13 Juny 2006 20:46, Tim Hochberg va escriure:
>
>
>>>Uh, I'm afraid that yes. In PyTables, int64, while being a bit bizarre for
>>>some users (specially in 32-bit platforms), is a type with the same rights
>>>than the others and we would like to give support for
On Tue, 13 Jun 2006 21:30:41 +0200
Francesc Altet <[EMAIL PROTECTED]> wrote:
> A Dimarts 13 Juny 2006 20:46, Tim Hochberg va escriure:
> > >Uh, I'm afraid that yes. In PyTables, int64, while being a bit bizarre
> > >for some users (specially in 32-bit platforms), is a type with the same
> > >right
A Dimarts 13 Juny 2006 20:46, Tim Hochberg va escriure:
> >Uh, I'm afraid that yes. In PyTables, int64, while being a bit bizarre for
> >some users (specially in 32-bit platforms), is a type with the same rights
> >than the others and we would like to give support for it in numexpr. In
> > fact, Iv
Francesc Altet wrote:
>Ei, numexpr seems to be back, wow! :-D
>
>A Dimarts 13 Juny 2006 18:56, Tim Hochberg va escriure:
>
>
>>I've finally got around to looking at numexpr again. Specifically, I'm
>>looking at Francesc Altet's numexpr-0.2, with the idea of harmonizing
>>the two versions. Let me
A Dimarts 13 Juny 2006 19:47, Francesc Altet va escriure:
> > - Support for both numpy and numarray (use the flag --force-numarray
> > in setup.py).
> >
> > At first glance this looks like it doesn't make things to messy, so I'm
> > in favor of incorporating this.
>
> Yeah. I thing you are
Ei, numexpr seems to be back, wow! :-D
A Dimarts 13 Juny 2006 18:56, Tim Hochberg va escriure:
> I've finally got around to looking at numexpr again. Specifically, I'm
> looking at Francesc Altet's numexpr-0.2, with the idea of harmonizing
> the two versions. Let me go through his list of enhancem
David M. Cooke wrote:
>On Tue, Jun 13, 2006 at 09:56:37AM -0700, Tim Hochberg wrote:
>
>
>>[SNIP]
>>
>>
>
>All the above is checked in already :-)
>
>
So I see. Oops!
>
>
>> - Support for both numpy and numarray (use the flag --force-numarray
>> in setup.py).
>>
>>At first glance th
On Tue, Jun 13, 2006 at 09:56:37AM -0700, Tim Hochberg wrote:
>
> I've finally got around to looking at numexpr again. Specifically, I'm
> looking at Francesc Altet's numexpr-0.2, with the idea of harmonizing
> the two versions. Let me go through his list of enhancements and comment
> (my comme
Oops! Having just done an svn update, I now see that David appears to
have done most of this about a week ago...
I'm behind the times.
-tim
Tim Hochberg wrote:
>I've finally got around to looking at numexpr again. Specifically, I'm
>looking at Francesc Altet's numexpr-0.2, with the idea of h
I've finally got around to looking at numexpr again. Specifically, I'm
looking at Francesc Altet's numexpr-0.2, with the idea of harmonizing
the two versions. Let me go through his list of enhancements and comment
(my comments are dedented):
- Addition of a boolean type. This allows better
[EMAIL PROTECTED] wrote:
> On 10.06.2006, at 01:57, Travis Oliphant wrote:
>
>
>> You may be interested to note that I just added the RNG interface
>> to numpy for back-wards compatibility. It can be accessed and used
>> by re-placing
>>
>> import RNG
>>
>> with
>>
>> import numpy.random.ol
[EMAIL PROTECTED] wrote:
> On 10.06.2006, at 01:57, Travis Oliphant wrote:
>
>>You may be interested to note that I just added the RNG interface
>>to numpy for back-wards compatibility. It can be accessed and used
>>by re-placing
>>
>>import RNG
>>
>>with
>>
>>import numpy.random.oldrng as RN
On 10.06.2006, at 01:57, Travis Oliphant wrote:
> You may be interested to note that I just added the RNG interface
> to numpy for back-wards compatibility. It can be accessed and used
> by re-placing
>
> import RNG
>
> with
>
> import numpy.random.oldrng as RNG
Thanks, that will facilitate
___
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion
On Tue, Jun 13, 2006 at 01:41:17AM +0100, stephen emslie wrote:
> I have used adaptive thresholding to turn an image into a binary image
> so that I can locate a particularly large bright spot. However, now
> that I have the binary image I need to be able to group connected
> cell's together and de
19 matches
Mail list logo
