Looks like the web site & svn are up for me.
Bryce
Fernando Perez wrote:
> Any chance it might be brought back up? (I'm trying to commit the
> weave cleanup work Min did at the sprint...)
>
> Thanks,
>
> f
> ___
> Numpy-discussion mailing list
> Numpy-d
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
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 capable of generating SConscript files
from setup.py scr
I can confirm that our python 2.4 numpy and scipy eggs (and probably
matplotlib and others) work with Vista. I was using them for development
last week. I haven't tested the Python 2.5 eggs yet, but will do so this
week. You can find all of our python 2.4 eggs at
http://code.enthought.com/ensta
Ryan,
The VMWare player is the best starting point. Just download and install
the player, then get an image from somewhere (you can find a plethora of
them on the VMWare web site). After downloading the image, its as simple
as double clicking on the file in explorer or launching it via the sta
Yup, we've decided to write custom concatenate & where methods. Thanks
for all the help.
Bryce
Pierre GM wrote:
On Thursday 29 March 2007 14:09:38 Bryce Hendrix wrote:
I really should widen my tests before proclaiming success... If you
change the default units to "feet&q
wrote:
On Thursday 29 March 2007 13:47:48 Bryce Hendrix wrote:
doh! I followed the example on the Wiki which does not define the class
attribute in the class scope, but in __new__. Adding the declaration to
the class scope seems to work.
Yeah, sorry about that, I really should update this wi
I really should widen my tests before proclaiming success... If you
change the default units to "feet", the result of concatenating two
UnitArrays instances with "meters" units is a UnitArray with "feet".
Bryce
Pierre GM wrote:
On Thursday 29 March 2007 12:04
doh! I followed the example on the Wiki which does not define the class
attribute in the class scope, but in __new__. Adding the declaration to
the class scope seems to work.
Thanks,
Bryce
Pierre GM wrote:
On Thursday 29 March 2007 12:04:51 Bryce Hendrix wrote:
I spoke too soon, this
calls __new__ with different units
unit_ary_3 = UnitArray(numpy.array((1,2,3)), units=feet)
new_unit_ary = numpy.concatenate([unit_ary_1, unit_ary_2])
self.assertEqual(new_unit_ary.units, meters)
Any other ideas?
Bryce
Pierre GM wrote:
On Wednesday 28 March 2007 12:42:52 Bryce Hendrix wrote
Thanks Pierre, works like a charm. One question though, how is defining
a class attribute in __new__ any more thread-safe?
Bryce
Pierre GM wrote:
On Tuesday 27 March 2007 20:08:04 Bryce Hendrix wrote:
We have a class which is a subclass of ndarray which defines
__array_finalize__ to add
We have a class which is a subclass of ndarray which defines
__array_finalize__ to add an attribute. The class looks something like
this:
class UnitArray(ndarray):
# ...
def __new__(cls, data, dtype=None, copy=True, units=None):
# ...
arr = array(data, dtype=dtype, copy=copy)
res = nd
12 matches
Mail list logo
