Geoffrey Zhu wrote:
Yes, with the MSI I can always reproduce the problem with
numpy.test(). It always hangs.With the egg it does not hang. Pointer
problems are usually random, but not random if we are using the same
binaries in EGG and MSI and variables are always initialized to
certain
Yes, with the MSI I can always reproduce the problem with
numpy.test(). It always hangs.With the egg it does not hang. Pointer
problems are usually random, but not random if we are using the same
binaries in EGG and MSI and variables are always initialized to
certain value.
I can
On Nov 13, 2007 6:30 AM, Travis E. Oliphant [EMAIL PROTECTED] wrote:
David Cournapeau wrote:
snip
I'm also interested in moving scipy.weave into numpy (without the blitz
converters which will stay in scipy).
Hi,
I'm excited to hear that weave would get elevated to a more exposed place !
Hi Sebastian
On Tue, Nov 13, 2007 at 01:11:33PM +0100, Sebastian Haase wrote:
Hi,
I need to check the array dtype in a way that it is ignoring
differences coming only from big-endian vs. little-endian.
Does
N.issubdtype(first_dtype, second_dtype)
work?
Cheers
Stéfan
Hi all,
Would it make sense for all functionality in Numpy/Scipy to have
ubiquitous returns? In that I'm proposing that every func/method
(where appropriate) have a flag in its arg list establishing a return
for either [INDEX, BOOLEAN, VALUE=default]. this could be by a
singular Enum flag, I
On Nov 13, 2007 2:18 PM, Stefan van der Walt [EMAIL PROTECTED] wrote:
Hi Sebastian
On Tue, Nov 13, 2007 at 01:11:33PM +0100, Sebastian Haase wrote:
Hi,
I need to check the array dtype in a way that it is ignoring
differences coming only from big-endian vs. little-endian.
Does
On Nov 13, 2007 2:18 PM, Stefan van der Walt [EMAIL PROTECTED] wrote:
Hi Sebastian
On Tue, Nov 13, 2007 at 01:11:33PM +0100, Sebastian Haase wrote:
Hi,
I need to check the array dtype in a way that it is ignoring
differences coming only from big-endian vs. little-endian.
Does
Please see the other active thread on this topic on the scipy-users
list. This is a known issue.
Brian
On Nov 12, 2007 10:09 PM, Chris [EMAIL PROTECTED] wrote:
I've just upgraded my OSX system to Leopard, and have successfully build
numpy from scratch. I am trying to build some code, which
On Nov 13, 2007 6:57 AM, Sebastian Haase [EMAIL PROTECTED] wrote:
On Nov 13, 2007 2:18 PM, Stefan van der Walt [EMAIL PROTECTED] wrote:
Hi Sebastian
On Tue, Nov 13, 2007 at 01:11:33PM +0100, Sebastian Haase wrote:
Hi,
I need to check the array dtype in a way that it is ignoring
On Nov 10, 2007 3:33 PM, Michael McNeil Forbes [EMAIL PROTECTED]
wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? I know that the behaviour can be controlled by
seterr(), but it seem rather unpythonic not to use the warnings library.
Is there an
Michael McNeil Forbes wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? I know that the behaviour can be controlled by
seterr(), but it seem rather unpythonic not to use the warnings library.
The warn option explicitly allows you to use the
On Nov 12, 2007 10:51 AM, David Cournapeau [EMAIL PROTECTED] wrote:
On Nov 13, 2007 3:37 AM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate on my machine,
which was not
dieter h. wrote:
Hi all,
Would it make sense for all functionality in Numpy/Scipy to have
ubiquitous returns? In that I'm proposing that every func/method
(where appropriate) have a flag in its arg list establishing a return
for either [INDEX, BOOLEAN, VALUE=default]. this could be by a
On Nov 13, 2007 2:37 AM, David Cournapeau [EMAIL PROTECTED] wrote:
Geoffrey Zhu wrote:
Yes, with the MSI I can always reproduce the problem with
numpy.test(). It always hangs.With the egg it does not hang. Pointer
problems are usually random, but not random if we are using the same
On 13 Nov 2007, at 8:46 AM, Travis E. Oliphant wrote:
Michael McNeil Forbes wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? ... in util.py ...
The warn option explicitly allows you to use the warnings library.
There is already the print mode
On Nov 13, 2007 11:48 AM, Michael McNeil Forbes [EMAIL PROTECTED]
wrote:
On 13 Nov 2007, at 8:46 AM, Travis E. Oliphant wrote:
Michael McNeil Forbes wrote:
Why are numpy warnings printed rather than issued using the standard
warnings library? ... in util.py ...
The warn option
Keith Goodman wrote:
On Nov 12, 2007 10:51 AM, David Cournapeau [EMAIL PROTECTED] wrote:
On Nov 13, 2007 3:37 AM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate
17 matches
Mail list logo
