Hi,
I spent the last WE trying to understand the whole numpy build
process (all this related to my project of sconsification of numpy).
One thing which I came across, and is a bit problematic is the fact that
numpy/core build process relies on a config.h which is meant to be
distributed
We've created a Google Group to discuss this project, and if anyone's
interested in contributing or advising, you're very welcome to sign up:
http://groups.google.com/group/c-extensions-for-ironpython/
My replies to everyone's comments below:
David Cournapeau wrote:
Giles, maybe you could
Hi,
there is a way of doing this. As far as I know, you have to create
your own version of numpy arrays. E. g. try this:
class myNumpy(numpy.ndarray):
pass
Then creating an instance as in
a = myNumpy(otherNumpyArray)
would make `a` behave just like any other array, except that you CAN
On Tuesday 16 October 2007 11:47:35 Sebastian Haase wrote:
Hi,
there is a way of doing this. As far as I know, you have to create
your own version of numpy arrays. E. g. try this:
...
Be carefull that some (many / most ?) operations on that array will
return you a normal numpy array again.
Sebastian Haase wrote:
Hi,
there is a way of doing this. As far as I know, you have to create
your own version of numpy arrays. E. g. try this:
class myNumpy(numpy.ndarray):
pass
Then creating an instance as in
a = myNumpy(otherNumpyArray)
would make `a` behave just like any other
David Cournapeau wrote:
Bryce Hendrix wrote:
I've only been following this thread on the perimeter, so I'm not sure
if makefile migration has been discussed. I have a script I wrote
about a year ago when we (Enthought) were looking at using SCons for our
internal builds. The script is
Hello,
First of all, I'm sorry if this question had already been asked. I've
searched on the gmane archive and elsewhere on internet, but I didn't found
the answer to my question.
As expected, the dot product of 2 'classical' vectors works fine :
In [50]: a0 = numpy.array([1,2,3])
In [51]:
On 10/17/07, Julien Hillairet [EMAIL PROTECTED] wrote:
Hello,
First of all, I'm sorry if this question had already been asked. I've
searched on the gmane archive and elsewhere on internet, but I didn't found
the answer to my question.
As expected, the dot product of 2 'classical' vectors
On 10/16/07, Julien Hillairet [EMAIL PROTECTED] wrote:
Hello,
First of all, I'm sorry if this question had already been asked. I've
searched on the gmane archive and elsewhere on internet, but I didn't found
the answer to my question.
As expected, the dot product of 2 'classical' vectors
Julien Hillairet wrote:
Hello,
First of all, I'm sorry if this question had already been asked. I've
searched on the gmane archive and elsewhere on internet, but I didn't
found the answer to my question.
As expected, the dot product of 2 'classical' vectors works fine :
In [50]: a0 =
2007/10/16, Bill Baxter [EMAIL PROTECTED]:
dot() also serves as Numpy's matrix multiply function. So it's trying
to interpret that as a (3,N) matrix times a (3,N) matrix.
See examples here:
http://www.scipy.org/Numpy_Example_List_With_Doc#head-2a810f7dccd3f7c700d1076f15078ad1fe3c6d0d
On 10/16/07, Julien Hillairet [EMAIL PROTECTED] wrote:
2007/10/16, Bill Baxter [EMAIL PROTECTED]:
dot() also serves as Numpy's matrix multiply function. So it's trying
to interpret that as a (3,N) matrix times a (3,N) matrix.
See examples here:
12 matches
Mail list logo