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
Oliver Siemoneit wrote:
> # Transform to LMS space
> LMS = numpy.zeros_like(RGB)
> for i in range(RGB.shape[0]):
> for j in range(RGB.shape[1]):
> rgb = RGB[i,j,:2]
> LMS[i,j,:2] = numpy.dot(rgb2lms, rgb)
>
> This code fails in the last line with the er
Dear numpy experts!
I'm just trying to port some matlab algorithm to python which allows an
image correction for color blind users. If I succeed this bit of code might
be part of the MoinMoin wiki, the wikisoftware scipy.org uses (see for more
on that http://moinmoin.wikiwikiweb.de/AccessibleMo
Tyler J Hayes wrote:
> I'm not sure if this will help, but have you tried to specify the gfortran
> compiler via the option:
>
> --fcompiler=gnu95
>
> when calling f2py in the second line after the ".pyf" file has been
> created? Perhaps that will work.
Sorry for late response, Tyler. But this
Anton Sherwood wrote:
> When I try to build numpy (or PIL) on MacOS, I get this error:
> "gcc: cannot specify -o with -c or -S and multiple compilations"
>
> Assuming at least one of you is using numpy on MacOS,
> how did you get around that?
by installing a binary from:
pythonmac.org/packages
O
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
I think that error went away when I used the latest developer tools from
Apple, and made sure I was using gcc4.
Take a look at:
http://www.scipy.org/Installing_SciPy/Mac_OS_X
Vincent
On 4/12/07 1:19 AM, "Anton Sherwood" <[EMAIL PROTECTED]> wrote:
> When I try to build numpy (or PIL) on MacOS,
Bernhard Voigt wrote:
> Dear all!
>
> in a 2-dim array I would like to select rows specified by a list of
> indexes and from these rows I'd like to select columns specified by
> another list of indexes. That's what I found as a solution:
>
> In [90]: a = arange(15).reshape(5,3)
> In [91]: a
> Out
Dear all!
in a 2-dim array I would like to select rows specified by a list of indexes
and from these rows I'd like to select columns specified by another list of
indexes. That's what I found as a solution:
In [90]: a = arange(15).reshape(5,3)
In [91]: a
Out[91]:
array([[ 0, 1, 2],
[ 3,
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
11 matches
Mail list logo