Stefan van der Walt wrote:
> Would such a scheme cause problems for anyone?
Yes. Don't check in tests that fail. If you want to keep around a test file for
a feature that's in development, put it elsewhere. You can make a directory in
branches/ if you like (it doesn't actually have to be a full br
On Thu, Apr 12, 2007 at 11:29:31AM -0400, Anne Archibald wrote:
> > Failures may be expressed using
> >
> > NumpyTestCase.failIf(self, expr, msg=None)
>
> That's not quite what I mean. There are situations, with the current
> code, that it gets the answer wrong (i.e., claims arrays may share
> mem
On 12/04/07, Stefan van der Walt <[EMAIL PROTECTED]> wrote:
> Thank you for taking the time to write those tests!
>
> Failures may be expressed using
>
> NumpyTestCase.failIf(self, expr, msg=None)
That's not quite what I mean. There are situations, with the current
code, that it gets the answer w
On Wed, Apr 11, 2007 at 11:06:13PM -0400, Anne Archibald wrote:
> On 11/04/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
>
> >Must be pretty recent. I'm using 1.0.2.dev3520 (enthought egg) and
> >the function's not there.
>
> It is.
>
> I've never been quite happy with it, though; I realize it's n
On 11/04/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
Must be pretty recent. I'm using 1.0.2.dev3520 (enthought egg) and
the function's not there.
It is.
I've never been quite happy with it, though; I realize it's not very
feasible to write one that efficiently checks all possible overlaps,
bu
On 4/12/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
>
>
> Bill Baxter wrote:
>
> > But maybe that's pretty much what may_share_memory does?
>
> I think so. Travis added it after a discussion much like this one on the
> list.
Must be pretty recent. I'm using 1.0.2.dev3520 (enthought egg) and
Bill Baxter wrote:
> But maybe that's pretty much what may_share_memory does?
I think so. Travis added it after a discussion much like this one on the
list.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R(206) 526-6959 voice
7600 S
On 4/12/07, Matthew Koichi Grimes <[EMAIL PROTECTED]> wrote:
> It's better than nothing. I basically want some sanity-check assert code
> that can assert that some arrays are in fact sub-arrays of another
> array. Your OWNDATA suggestion meets me halfway by allowing me to check
> that these sub-arr
It's better than nothing. I basically want some sanity-check assert code
that can assert that some arrays are in fact sub-arrays of another
array. Your OWNDATA suggestion meets me halfway by allowing me to check
that these sub-arrays are at least sub-arrays of *someone*.
Thanks,
-- Matt
Pierre
On Wed, Apr 11, 2007 at 06:12:16PM -0400, Matthew Koichi Grimes wrote:
> Is there any way to detect whether one array is a view into another
> array? I'd like something like:
>
> >>> arr = N.arange(5)
> >>> subarr = arr[1:3]
> >>> sharesdata(arr, subarr)
> True
Your best bet is probably
N.ma
On Wednesday 11 April 2007 18:12:16 Matthew Koichi Grimes wrote:
> Is there any way to detect whether one array is a view into another
>
> array? I'd like something like:
> >>> arr = N.arange(5)
> >>> subarr = arr[1:3]
> >>> sharesdata(arr, subarr)
Mmh, would arr.flags['OWNDATA'] would do the t
Is there any way to detect whether one array is a view into another
array? I'd like something like:
>>> arr = N.arange(5)
>>> subarr = arr[1:3]
>>> sharesdata(arr, subarr)
True
-- Matt
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
htt
12 matches
Mail list logo
