[Numpy-discussion] test

checking if server works as expected after SSL cert update ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi Julian, to distinguish between mingw32 and mingw-w64 we need something like this: #include if !defined(HAVE_EXPM1) || defined(__MINGW64_VERSION_MAJOR) instead of if !defined(HAVE_EXPM1) || defined(__MINGW32__) the latter is true for both: mingw32 and mingw-w64. I guess the mingw32 implemen

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, On Wed, Apr 23, 2014 at 2:27 PM, Julian Taylor wrote: > On 23.04.2014 21:25, Matthew Brett wrote: >> Hi, >> >> On Tue, Apr 15, 2014 at 12:34 AM, Julian Taylor >> wrote: >>> On Tue, Apr 15, 2014 at 4:30 AM, Matthew Brett >>> wrote: It looks as though mingw-w64 is at fault, and I w

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On 23.04.2014 21:25, Matthew Brett wrote: > Hi, > > On Tue, Apr 15, 2014 at 12:34 AM, Julian Taylor > wrote: >> On Tue, Apr 15, 2014 at 4:30 AM, Matthew Brett >> wrote: >>> >>> It looks as though mingw-w64 is at fault, and I was confused (still >>> am) because of the different behavior with dou

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, On Tue, Apr 15, 2014 at 12:34 AM, Julian Taylor wrote: > On Tue, Apr 15, 2014 at 4:30 AM, Matthew Brett > wrote: >> >> It looks as though mingw-w64 is at fault, and I was confused (still >> am) because of the different behavior with double and a constant: >> >> #include >> #include >> >>

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On Tue, Apr 15, 2014 at 4:30 AM, Matthew Brett wrote: > > It looks as though mingw-w64 is at fault, and I was confused (still > am) because of the different behavior with double and a constant: > > #include > #include > > int main() { > double z, i = -0.0; > printf("With double %f=%f, wi

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On Mon, Apr 14, 2014 at 5:01 PM, Matthew Brett wrote: > Hi, > > On Mon, Apr 14, 2014 at 3:55 PM, Charles R Harris > wrote: >> >> >> >> On Mon, Apr 14, 2014 at 4:40 PM, Matthew Brett >> wrote: >>> >>> Hi, >>> >>> On Mon, Apr 14, 2014 at 2:58 PM, Charles R Harris >>> wrote: >>> > >>> > >>> > >>>

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, On Mon, Apr 14, 2014 at 3:55 PM, Charles R Harris wrote: > > > > On Mon, Apr 14, 2014 at 4:40 PM, Matthew Brett > wrote: >> >> Hi, >> >> On Mon, Apr 14, 2014 at 2:58 PM, Charles R Harris >> wrote: >> > >> > >> > >> > On Mon, Apr 14, 2014 at 3:38 PM, Matthew Brett >> > wrote: >> >> >> >> Hi

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On Mon, Apr 14, 2014 at 4:40 PM, Matthew Brett wrote: > Hi, > > On Mon, Apr 14, 2014 at 2:58 PM, Charles R Harris > wrote: > > > > > > > > On Mon, Apr 14, 2014 at 3:38 PM, Matthew Brett > > wrote: > >> > >> Hi, > >> > >> On Mon, Apr 14, 2014 at 2:02 PM, Julian Taylor > >> wrote: > >> > The offi

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, On Mon, Apr 14, 2014 at 2:58 PM, Charles R Harris wrote: > > > > On Mon, Apr 14, 2014 at 3:38 PM, Matthew Brett > wrote: >> >> Hi, >> >> On Mon, Apr 14, 2014 at 2:02 PM, Julian Taylor >> wrote: >> > The official numpy mingw binaries do not have all these math issues. >> > Only the VC builds

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On Mon, Apr 14, 2014 at 10:02 PM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > The official numpy mingw binaries do not have all these math issues. > Only the VC builds do. > As mingw is fine the functions must be somewhere in the windows API but > no-one has contributed a fix for the V

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On Mon, Apr 14, 2014 at 3:38 PM, Matthew Brett wrote: > Hi, > > On Mon, Apr 14, 2014 at 2:02 PM, Julian Taylor > wrote: > > The official numpy mingw binaries do not have all these math issues. > > Only the VC builds do. > > As mingw is fine the functions must be somewhere in the windows API but >

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, On Mon, Apr 14, 2014 at 2:02 PM, Julian Taylor wrote: > The official numpy mingw binaries do not have all these math issues. > Only the VC builds do. > As mingw is fine the functions must be somewhere in the windows API but > no-one has contributed a fix for the VC builds to numpy yet. I'm b

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

The official numpy mingw binaries do not have all these math issues. Only the VC builds do. As mingw is fine the functions must be somewhere in the windows API but no-one has contributed a fix for the VC builds to numpy yet. On 14.04.2014 22:43, Carl Kleffner wrote: > Hi, > > mingw has expm1. Is

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, mingw has expm1. Is this function suitable? Regards Carl 2014-04-14 21:34 GMT+02:00 Eric Moore : > > > On Monday, April 14, 2014, Matthew Brett wrote: > >> Hi, >> >> On Mon, Apr 14, 2014 at 12:12 PM, Warren Weckesser >> wrote: >> > >> > On Mon, Apr 14, 2014 at 2:59 PM, Matthew Brett >

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On Monday, April 14, 2014, Matthew Brett wrote: > Hi, > > On Mon, Apr 14, 2014 at 12:12 PM, Warren Weckesser > > wrote: > > > > On Mon, Apr 14, 2014 at 2:59 PM, Matthew Brett > > > > > > wrote: > >> > >> Hi, > >> > >> With Carl Kleffner, I am trying to build a numpy 1.8.1 wheel for > >> Windows

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, On Mon, Apr 14, 2014 at 12:12 PM, Warren Weckesser wrote: > > On Mon, Apr 14, 2014 at 2:59 PM, Matthew Brett > wrote: >> >> Hi, >> >> With Carl Kleffner, I am trying to build a numpy 1.8.1 wheel for >> Windows 64-bit, and latest stable ATLAS. >> >> It works fine, apart from the following tes

Re: [Numpy-discussion] Test error with ATLAS, Windows 64 bit

On Mon, Apr 14, 2014 at 2:59 PM, Matthew Brett wrote: > Hi, > > With Carl Kleffner, I am trying to build a numpy 1.8.1 wheel for > Windows 64-bit, and latest stable ATLAS. > > It works fine, apart from the following test failure: > >

[Numpy-discussion] Test error with ATLAS, Windows 64 bit

Hi, With Carl Kleffner, I am trying to build a numpy 1.8.1 wheel for Windows 64-bit, and latest stable ATLAS. It works fine, apart from the following test failure: == FAIL: test_special (test_umath.TestExpm1) ---

[Numpy-discussion] Test cases for integer behvaiour

Hi All, For scalar operations Numpy first try to extract the underlying C value from a Python Integers. It causes bottleneck because it first converts the Python scalar into its matching NumPy scalar (e.g. PyLong -> int32) and then it extracts the C value from the NumPy scalar. Its quicker to jus

Re: [Numpy-discussion] test failures when embedded (in matlab)

On Thu, Jan 3, 2013 at 7:54 AM, Robin wrote: > Hi All, > > When using Numpy from an embedded Python (Python embedded in a Matlab > mex function) I get a lot of test failures (see attached log). > > I am using CentOS 6.3, distribution packaged Python (2.6) and Numpy > (1.4.1). Running numpy tests f

Re: [Numpy-discussion] Test failures on Windows XP 64-bit

On Wed, Jul 25, 2012 at 3:03 AM, Ondřej Čertík wrote: > Hi, > > I've created a Windows installer of the maintenance/1.7.x branch > (commit f93774d), the binary is available here (created in Wine on > linux): > > > https://github.com/certik/numpy-vendor/blob/69555c40dff5ae9f2d27d827f283bc6d9c53fccf

[Numpy-discussion] Test failures on Windows XP 64-bit

Hi, I've created a Windows installer of the maintenance/1.7.x branch (commit f93774d), the binary is available here (created in Wine on linux): https://github.com/certik/numpy-vendor/blob/69555c40dff5ae9f2d27d827f283bc6d9c53fccf/test/ and when I install it on the Windows XP 64-bit machine, here

Re: [Numpy-discussion] Test failures - which dependencies am I missing?

Chris Ball gmail.com> writes: > > Keith Hughitt gmail.com> writes: > > > Hi Chris, > > > > Try "sudo apt-get build-dep python-numpy" to install the dependencies for > > building NumPy. I believe it will install all of the optional dependencies > > as well. > > Thanks for that, but I'd alrea

Re: [Numpy-discussion] Test failures - which dependencies am I missing?

On Tue, May 1, 2012 at 5:20 PM, Chris Ball wrote: > Keith Hughitt gmail.com> writes: > > > Hi Chris, > > > > Try "sudo apt-get build-dep python-numpy" to install the dependencies for > > building NumPy. I believe it will install all of the optional > dependencies > > as well. > > Thanks for that

Re: [Numpy-discussion] Test failures - which dependencies am I missing?

Keith Hughitt gmail.com> writes: > Hi Chris, > > Try "sudo apt-get build-dep python-numpy" to install the dependencies for > building NumPy. I believe it will install all of the optional dependencies > as well. Thanks for that, but I'd already tried it and found the same failures. However, I

Re: [Numpy-discussion] Test failures - which dependencies am I missing?

Hi Chris, Try "sudo apt-get build-dep python-numpy" to install the dependencies for building NumPy. I believe it will install all of the optional dependencies as well. HTH, Keith ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.s

[Numpy-discussion] Test failures - which dependencies am I missing?

Hi, When I build NumPy and then run the tests on Ubuntu (10.04 LTS) and Debian (6.1), I always seem to get several failures. I guess most of these failures come from not having some dependencies installed, but I can't figure out which ones by reading e.g. http://docs.scipy.org/doc/numpy/user/in

Re: [Numpy-discussion] test errors on deprecation/runtime warnings

On Sat, Feb 18, 2012 at 10:13 AM, Ralf Gommers wrote: > > > 2012/2/17 Stéfan van der Walt > >> Hi Ralf >> >> On Thu, Feb 16, 2012 at 11:05 AM, Ralf Gommers >> wrote: >> > Last week we merged https://github.com/numpy/numpy/pull/201, which >> causes >> > DeprecationWarning's and RuntimeWarning's t

Re: [Numpy-discussion] Test survey that I have been putting together

On 2/23/2012 7:20 PM, Travis Oliphant wrote: > https://www.surveymonkey.com/s/numpy_list_survey > After you complete the survey, I would really appreciate any feedback on > questions that could be improved, removed, or added. I felt the survey was targeting business users rather than academic u

Re: [Numpy-discussion] Test survey that I have been putting together

> From: Travis Oliphant > After you complete the survey, I would really appreciate any feedback on > questions that could be improved, removed, or added. Hi Travis, I didn't really get whom you mean by "they" in: 5. What do they want you to be using (technologies, languages, libraries)?

Re: [Numpy-discussion] Test survey that I have been putting together

Hi, Great idea ! What's the plan to spread the word about this survey ? Is it about forwarding the link to friends and colleagues ? Le 24/02/2012 01:20, Travis Oliphant a écrit : > After you complete the survey, I would really appreciate any feedback on > questions that could be improved, remove

[Numpy-discussion] Test survey that I have been putting together

Hey all, I would like to gather concrete information about NumPy users and have some data to look at regarding the user base and features that are of interest. We have been putting together a survey that I would love feedback on from members of this list. If you have time and are intere

Re: [Numpy-discussion] test errors on deprecation/runtime warnings

2012/2/17 Stéfan van der Walt > Hi Ralf > > On Thu, Feb 16, 2012 at 11:05 AM, Ralf Gommers > wrote: > > Last week we merged https://github.com/numpy/numpy/pull/201, which > causes > > DeprecationWarning's and RuntimeWarning's to be converted to errors if > they > > occur when running the test su

Re: [Numpy-discussion] test errors on deprecation/runtime warnings

Hi Ralf On Thu, Feb 16, 2012 at 11:05 AM, Ralf Gommers wrote: > Last week we merged https://github.com/numpy/numpy/pull/201, which causes > DeprecationWarning's and RuntimeWarning's to be converted to errors if they > occur when running the test suite. It looks like this change affects other pac

[Numpy-discussion] test errors on deprecation/runtime warnings

Hi, Last week we merged https://github.com/numpy/numpy/pull/201, which causes DeprecationWarning's and RuntimeWarning's to be converted to errors if they occur when running the test suite. The purpose of that is to make sure that code that still uses other deprecated code (or code that for some re

Re: [Numpy-discussion] test code for user defined types in numpy

On Wed, Dec 21, 2011 at 1:37 PM, Geoffrey Irving wrote: > On Wed, Dec 21, 2011 at 3:56 AM, Charles R Harris > wrote: > > Hi Geoffrey, > > > > On Tue, Dec 20, 2011 at 7:24 PM, Geoffrey Irving wrote: > >> > >> Hello, > >> > >> As a followup to the prior thread on bugs in user defined types in > >

Re: [Numpy-discussion] test code for user defined types in numpy

On Wed, Dec 21, 2011 at 3:56 AM, Charles R Harris wrote: > Hi Geoffrey, > > On Tue, Dec 20, 2011 at 7:24 PM, Geoffrey Irving wrote: >> >> Hello, >> >> As a followup to the prior thread on bugs in user defined types in >> numpy, I converted my rational number class from C++ to C and switched >> to

Re: [Numpy-discussion] test code for user defined types in numpy

On Tue, Dec 20, 2011 at 10:48 PM, Christopher Jordan-Squire wrote: > On Tue, Dec 20, 2011 at 9:10 PM, Mark Wiebe wrote: > > On Tue, Dec 20, 2011 at 6:24 PM, Geoffrey Irving wrote: > >> > >> Hello, > >> > >> As a followup to the prior thread on bugs in user defined types in > >> numpy, I convert

Re: [Numpy-discussion] test code for user defined types in numpy

Hi Geoffrey, On Tue, Dec 20, 2011 at 7:24 PM, Geoffrey Irving wrote: > Hello, > > As a followup to the prior thread on bugs in user defined types in > numpy, I converted my rational number class from C++ to C and switched > to 32 bits to remove the need for unportable 128 bit numbers. It > shou

Re: [Numpy-discussion] test code for user defined types in numpy

On Tue, Dec 20, 2011 at 9:10 PM, Mark Wiebe wrote: > On Tue, Dec 20, 2011 at 6:24 PM, Geoffrey Irving wrote: >> >> Hello, >> >> As a followup to the prior thread on bugs in user defined types in >> numpy, I converted my rational number class from C++ to C and switched >> to 32 bits to remove the

Re: [Numpy-discussion] test code for user defined types in numpy

On Tue, Dec 20, 2011 at 6:24 PM, Geoffrey Irving wrote: > Hello, > > As a followup to the prior thread on bugs in user defined types in > numpy, I converted my rational number class from C++ to C and switched > to 32 bits to remove the need for unportable 128 bit numbers. It > should be usable a

Re: [Numpy-discussion] test code for user defined types in numpy

This is really excellent. I would like to take a stab at getting this pulled in to the code base --- and fixing the GIL issue --- if someone hasn't beat me to it. Travis -- Travis Oliphant (on a mobile) 512-826-7480 On Dec 20, 2011, at 9:24 PM, Geoffrey Irving wrote: > Hello, > > As a fo

Re: [Numpy-discussion] test code for user defined types in numpy

On Tue, Dec 20, 2011 at 7:24 PM, Geoffrey Irving wrote: > Hello, > > As a followup to the prior thread on bugs in user defined types in > numpy, I converted my rational number class from C++ to C and switched > to 32 bits to remove the need for unportable 128 bit numbers. It > should be usable a

[Numpy-discussion] test code for user defined types in numpy

Hello, As a followup to the prior thread on bugs in user defined types in numpy, I converted my rational number class from C++ to C and switched to 32 bits to remove the need for unportable 128 bit numbers. It should be usable as a fairly thorough test case for user defined types now. It does ra

Re: [Numpy-discussion] Test failures on 2.6

On Oct 5, 2008, at 10:53 PM, T J wrote: > Hi, > > I'm getting a couple of test failures with Python 2.6, Numpy 1.2.0, Nose > 0.10.4: Wow, 1.2.0 ? That's fairly ancient. I gather the bugs in numpy.ma have been corrected since (they don't really look familiar, though). And with a more recent n

Re: [Numpy-discussion] Test failures on 2.6

I'm having almost exactly the same problem, but with Python 2.6.1, Numpy 1.2.1, and Nose 0.11.3. Nobody responded to TJ the first time around, so any advice would be greatly appreciated. Thanks, Brad -- From: T J gmail.com> Subj

Re: [Numpy-discussion] test failure

Thanks Ralf. This closes the issue for me. FYI When I set the precision to 4 I am able to repeat the test failure otherwise not. Its a bit odd the precision was changed somehow when I originally ran numpy.test() because I know that I didn't directly do that myself. >>> numpy.get_printoptions()

Re: [Numpy-discussion] test failure

On Sat, Oct 2, 2010 at 12:51 PM, John Mitchell wrote: > After spending a lot of time building 'numpy' (1.5.0) and 'scipy' (0.8.0) > I ran the following tests -- per what I read somewhere: > numpy.test() > > Out of several thousand small tests I found this one error -- perhaps its > not really an

[Numpy-discussion] test failure

After spending a lot of time building 'numpy' (1.5.0) and 'scipy' (0.8.0) I ran the following tests -- per what I read somewhere: numpy.test() Out of several thousand small tests I found this one error -- perhaps its not really an error? This doesn't look serious but it can be bothersome when o

Re: [Numpy-discussion] test for long double support

> Also look at CPython's objimpl.h, union _gc_head, you will see an > unprotected usage of 'long double', so it seems that CPython requires > that the C compiler to support 'long double'. Long double is IIRC in C89, so compiler support is probably not a problem nowadays. -- Pauli Virtanen _

Re: [Numpy-discussion] test for long double support

On 14 September 2010 12:47, Neal Becker wrote: > Neal Becker wrote: > >> What is the recommended way to test for long double and clongdouble? >> >> Is it: >> #if NPY_SIZEOF_LONGDOUBLE == NPY_SIZEOF_DOUBLE > > I guess I found it? > > #if HAVE_LONG_DOUBLE            // defined in pyconfig.h > I thi

Re: [Numpy-discussion] test for long double support

Neal Becker wrote: > What is the recommended way to test for long double and clongdouble? > > Is it: > #if NPY_SIZEOF_LONGDOUBLE == NPY_SIZEOF_DOUBLE I guess I found it? #if HAVE_LONG_DOUBLE// defined in pyconfig.h ___ NumPy-Discussion m

[Numpy-discussion] test for long double support

What is the recommended way to test for long double and clongdouble? Is it: #if NPY_SIZEOF_LONGDOUBLE == NPY_SIZEOF_DOUBLE ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test if two arrays share the same data

2010/9/5 Ernest Adrogué : >  5/09/10 @ 15:59 (-0500), thus spake Robert Kern: >> 2010/9/5 Ernest Adrogué : >> >  5/09/10 @ 21:25 (+0200), thus spake Gael Varoquaux: >> >> On Sun, Sep 05, 2010 at 09:12:34PM +0200, Ernest Adrogué wrote: >> >> > Hi, >> >> >> >> > How can it be done? >> >> >> >> np.may

Re: [Numpy-discussion] test if two arrays share the same data

5/09/10 @ 15:59 (-0500), thus spake Robert Kern: > 2010/9/5 Ernest Adrogué : > >  5/09/10 @ 21:25 (+0200), thus spake Gael Varoquaux: > >> On Sun, Sep 05, 2010 at 09:12:34PM +0200, Ernest Adrogué wrote: > >> > Hi, > >> > >> > How can it be done? > >> > >> np.may_share_memory > > > > Thanks Gael an

Re: [Numpy-discussion] test if two arrays share the same data

2010/9/5 Ernest Adrogué : >  5/09/10 @ 21:25 (+0200), thus spake Gael Varoquaux: >> On Sun, Sep 05, 2010 at 09:12:34PM +0200, Ernest Adrogué wrote: >> > Hi, >> >> > How can it be done? >> >> np.may_share_memory > > Thanks Gael and Puneeth. > I think the .base attribute is enough for what I want. N

Re: [Numpy-discussion] test if two arrays share the same data

5/09/10 @ 21:25 (+0200), thus spake Gael Varoquaux: > On Sun, Sep 05, 2010 at 09:12:34PM +0200, Ernest Adrogué wrote: > > Hi, > > > How can it be done? > > np.may_share_memory Thanks Gael and Puneeth. I think the .base attribute is enough for what I want. Bye :) > > __

Re: [Numpy-discussion] test if two arrays share the same data

On Sun, Sep 05, 2010 at 09:12:34PM +0200, Ernest Adrogué wrote: > Hi, > How can it be done? np.may_share_memory ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test if two arrays share the same data

2010/9/6 Ernest Adrogué : > Hi, > > How can it be done? > > id() doesn't do it: > > In [238]: a= np.arange(5) > > In [239]: id(a) == id(a[:]) > Out[239]: False > > Any ideas? Checking for a[:].base and a[:].size works. I'm not sure if that is a good way to do it. (a[:].base is a and a[:].size == a

[Numpy-discussion] test if two arrays share the same data

Hi, How can it be done? id() doesn't do it: In [238]: a= np.arange(5) In [239]: id(a) == id(a[:]) Out[239]: False Any ideas? Ernest ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test errors in the trunk

On Sat, Jul 31, 2010 at 7:22 AM, Ralf Gommers wrote: > > > On Sat, Jul 31, 2010 at 4:55 AM, Robert Kern wrote: >> >> On Fri, Jul 30, 2010 at 13:22, Darren Dale wrote: >> > I just upgraded my svn checkout and did a fresh install. When I try to >> > run the test suite, I get a ton of errors: >> >

Re: [Numpy-discussion] test errors in the trunk

On Sat, Jul 31, 2010 at 4:55 AM, Robert Kern wrote: > On Fri, Jul 30, 2010 at 13:22, Darren Dale wrote: > > I just upgraded my svn checkout and did a fresh install. When I try to > > run the test suite, I get a ton of errors: > > > > > > np.test() > > Running unit tests for numpy > > NumPy versi

Re: [Numpy-discussion] test errors in the trunk

On Fri, Jul 30, 2010 at 13:22, Darren Dale wrote: > I just upgraded my svn checkout and did a fresh install. When I try to > run the test suite, I get a ton of errors: > > > np.test() > Running unit tests for numpy > NumPy version 2.0.0.dev8550 > NumPy is installed in /Users/darren/.local/lib/pyth

[Numpy-discussion] test errors in the trunk

I just upgraded my svn checkout and did a fresh install. When I try to run the test suite, I get a ton of errors: np.test() Running unit tests for numpy NumPy version 2.0.0.dev8550 NumPy is installed in /Users/darren/.local/lib/python2.6/site-packages/numpy Python version 2.6.5 (r265:79063, Jul 1

Re: [Numpy-discussion] Test if one element of string array is in a defined list

Eric Emsellem eso.org> writes: > Hi > > I would like to test whether strings in a numpy S array are in a given list but > I don't manage to do so. Any hint is welcome. > > === > # So here is an example of what I would like to do > # I have a

[Numpy-discussion] Test if one element of string array is in a defined list

Hi I would like to test whether strings in a numpy S array are in a given list but I don't manage to do so. Any hint is welcome. === # So here is an example of what I would like to do # I have a String numpy array: import numpy as num Sarray =

[Numpy-discussion] Test reports of numpy 1.4.0.dev built with Visual Studio

Hello, I built Windows binaries of numpy-1.4.0rc2.dev7996 for Python 2.4, 2.5, and 2.6 (32 and 64-bit) using Microsoft Visual Studio 2003 and 2008. Looks good: the 'setup.py bdist_wininst' builds were all successful. The output of the 'python.exe -c "import numpy;numpy.test()"' runs are atta

Re: [Numpy-discussion] Test of numpy/py3k

Thanks, it works. Nadav On Mon, 2009-12-07 at 11:33 +0200, Pauli Virtanen wrote: > Hi, > > ma, 2009-12-07 kello 10:36 +0200, Nadav Horesh kirjoitti: > > I would like to test and prepare for migration of numpy/python3.1 on a > > linux box. > > Can anyone provide an installation recipe (and mayb

Re: [Numpy-discussion] Test of numpy/py3k

Hi, ma, 2009-12-07 kello 10:36 +0200, Nadav Horesh kirjoitti: > I would like to test and prepare for migration of numpy/python3.1 on a linux > box. > Can anyone provide an installation recipe (and maybe some more tips)? It should already "work out of the box": 1) Install Python 3 2) Install No

[Numpy-discussion] Test of numpy/py3k

I would like to test and prepare for migration of numpy/python3.1 on a linux box. Can anyone provide an installation recipe (and maybe some more tips)? Nadav. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/

Re: [Numpy-discussion] Test failures r7300

David Cournapeau wrote: > On Sat, Aug 8, 2009 at 10:33 PM, wrote: >> David Cournapeau wrote: >>> On Sat, Aug 8, 2009 at 9:38 PM, wrote: Hi, I got 16 test failures after building r7300 from svn on debian/sid/i386. Seems all related to complex linear algebra modules. >>> Are you

Re: [Numpy-discussion] Test failures r7300

On Sat, Aug 8, 2009 at 10:33 PM, wrote: > David Cournapeau wrote: >> On Sat, Aug 8, 2009 at 9:38 PM, wrote: >>> Hi, >>> >>> I got 16 test failures after building r7300 from svn on debian/sid/i386. >>> Seems all related to complex linear algebra modules. >> >> Are you using atlas ? (numpy.show_con

Re: [Numpy-discussion] Test failures r7300

David Cournapeau wrote: > On Sat, Aug 8, 2009 at 9:38 PM, wrote: >> Hi, >> >> I got 16 test failures after building r7300 from svn on debian/sid/i386. >> Seems all related to complex linear algebra modules. > > Are you using atlas ? (numpy.show_config() output) Yes, it's libatlas-sse2 3.6.0-24 d

Re: [Numpy-discussion] Test failures r7300

On Sat, Aug 8, 2009 at 9:38 PM, wrote: > Hi, > > I got 16 test failures after building r7300 from svn on debian/sid/i386. > Seems all related to complex linear algebra modules. Are you using atlas ? (numpy.show_config() output) If so, did you compile it by yourself ? Did you compile everything w

[Numpy-discussion] Test failures r7300

Hi, I got 16 test failures after building r7300 from svn on debian/sid/i386. Seems all related to complex linear algebra modules. Here's the error messages: Running unit tests for numpy NumPy version 1.4.0.dev7300 NumPy is installed in /var/opt/py/lib/python2.5/site-packages/numpy Python version

Re: [Numpy-discussion] Test failures for rev7299

On Fri, Aug 7, 2009 at 11:51 PM, David Cournapeau wrote: > Christopher Hanley wrote: >> Hi, >> >> I receive the following test errors after building numpy rev7229 from svn: >> > > Yep, a bug slipped in the last commit, I am fixing it right now, Hm, the fix does not look so obvious, so I just rever

Re: [Numpy-discussion] Test failures for rev7299

Christopher Hanley wrote: > Hi, > > I receive the following test errors after building numpy rev7229 from svn: > Yep, a bug slipped in the last commit, I am fixing it right now, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http:

[Numpy-discussion] Test failures for rev7299

Hi, I receive the following test errors after building numpy rev7229 from svn: == FAIL: test_simple_circular (test_multiarray.TestStackedNeighborhoodIter) -- Tra

Re: [Numpy-discussion] Test failures on FreeBSD buildbot

On Mon, Jul 27, 2009 at 10:48 PM, David Cournapeau < da...@ar.media.kyoto-u.ac.jp> wrote: > Charles R Harris wrote: > > > > I'd just look at the difference and see if it exceeded some fraction > > of the expected value. There is the problem of zero, which could be > > handled in the usual way as d

Re: [Numpy-discussion] Test failures on FreeBSD buildbot

Charles R Harris wrote: > > I'd just look at the difference and see if it exceeded some fraction > of the expected value. There is the problem of zero, which could be > handled in the usual way as diff < abserr + relerr. I think abserr > would need to be a new keyword with a default value. Since th

Re: [Numpy-discussion] Test failures on FreeBSD buildbot

On Mon, Jul 27, 2009 at 10:16 PM, David Cournapeau < da...@ar.media.kyoto-u.ac.jp> wrote: > Charles R Harris wrote: > > > > > > On Mon, Jul 27, 2009 at 9:37 PM, David Cournapeau > > wrote: > > > > On Tue, Jul 28, 2009 at 8:44 AM, Charles R > > Harris >

Re: [Numpy-discussion] Test failures on FreeBSD buildbot

Charles R Harris wrote: > > > On Mon, Jul 27, 2009 at 9:37 PM, David Cournapeau > wrote: > > On Tue, Jul 28, 2009 at 8:44 AM, Charles R > Harris > wrote: > > > ERROR: test_nan_items (test_utils.TestApproxEqual) > > >

Re: [Numpy-discussion] Test failures on FreeBSD buildbot

On Mon, Jul 27, 2009 at 9:37 PM, David Cournapeau wrote: > On Tue, Jul 28, 2009 at 8:44 AM, Charles R > Harris wrote: > > > ERROR: test_nan_items (test_utils.TestApproxEqual) > > -- > > Traceback (most recent call last): > > Fil

Re: [Numpy-discussion] Test failures on FreeBSD buildbot

On Tue, Jul 28, 2009 at 8:44 AM, Charles R Harris wrote: > ERROR: test_nan_items (test_utils.TestApproxEqual) > -- > Traceback (most recent call last): > File > "/tmp/numpy-buildbot/b12/numpy-install/lib/python2.5/site-packages/

[Numpy-discussion] Test failures on FreeBSD buildbot

== ERROR: test_nan_array (test_utils.TestApproxEqual) -- Traceback (most recent call last): File "/tmp/numpy-buildbot/b12/numpy-install/lib/python2.5/site-packa

Re: [Numpy-discussion] Test: My replies do not apear on the list

This showed up on numpy-discussion. I posted this morning and it hasn't appeared yet. Ian Nadav Horesh wrote: > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > -- Ian St

[Numpy-discussion] Test: My replies do not apear on the list

___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Test bug in reduceat with structured arrays copied for speed.

On 2009-06-19, Nils Wagner wrote: > Is this a known failure ? > I am using 1.4.0.dev7069 Check the tickets: http://projects.scipy.org/numpy/ticket/1108 Cause is not known yet, but that bug most likely has been around for a long time. -- Pauli Virtanen ___

[Numpy-discussion] Test bug in reduceat with structured arrays copied for speed.

Hi all, Is this a known failure ? I am using 1.4.0.dev7069 == FAIL: Test bug in reduceat with structured arrays copied for speed. -- Traceback (most recent call

Re: [Numpy-discussion] test failure in numpy trunk

On Tue, Mar 24, 2009 at 1:12 PM, Pauli Virtanen wrote: > Tue, 24 Mar 2009 13:15:21 -0400, Darren Dale wrote: > > I just performed an svn update, deleted my old build/ and > > site-packages/numpy*, reinstalled, and I see a new test failure on a 64 > > bit linux machine: > > > > ===

Re: [Numpy-discussion] test failure in numpy trunk

Tue, 24 Mar 2009 13:15:21 -0400, Darren Dale wrote: > I just performed an svn update, deleted my old build/ and > site-packages/numpy*, reinstalled, and I see a new test failure on a 64 > bit linux machine: > > == > FAIL: test_uma

Re: [Numpy-discussion] test failure in numpy trunk

2009/3/24 Charles R Harris > > > 2009/3/24 Darren Dale > > Hello, >> >> I just performed an svn update, deleted my old build/ and >> site-packages/numpy*, reinstalled, and I see a new test failure on a 64 bit >> linux machine: >> >> ===

Re: [Numpy-discussion] test failure in numpy trunk

On Tue, 24 Mar 2009 11:20:53 -0600 Charles R Harris wrote: > 2009/3/24 Darren Dale > >> Hello, >> >> I just performed an svn update, deleted my old build/ >>and >> site-packages/numpy*, reinstalled, and I see a new test >>failure on a 64 bit >> linux machine: >> >> ==

Re: [Numpy-discussion] test failure in numpy trunk

2009/3/24 Darren Dale > Hello, > > I just performed an svn update, deleted my old build/ and > site-packages/numpy*, reinstalled, and I see a new test failure on a 64 bit > linux machine: > > == > FAIL: test_umath.TestComplexFunc

[Numpy-discussion] test failure in numpy trunk

Hello, I just performed an svn update, deleted my old build/ and site-packages/numpy*, reinstalled, and I see a new test failure on a 64 bit linux machine: == FAIL: test_umath.TestComplexFunctions.test_loss_of_precision_longcompl

[Numpy-discussion] Test failures on 2.6

Hi, I'm getting a couple of test failures with Python 2.6, Numpy 1.2.0, Nose 0.10.4: nose version 0.10.4 ..

Re: [Numpy-discussion] test results of 1.2.0rc1

Thu, 04 Sep 2008 19:07:24 +, Pauli Virtanen wrote: [clip] > I'd say that the settings are "unintended" in the sense that they run > all examples in all docstrings. There are quite a few of these, and some > indeed plot some graphs. > > Ideally, all examples should run, but this is not assured

Re: [Numpy-discussion] test results of 1.2.0rc1

Thu, 04 Sep 2008 11:51:14 -0700, Andrew Straw wrote: > Hi, with numpy 1.2.0rc1 running 'python -c "import numpy; numpy.test()"' > on my Ubuntu Hardy amd64 machine results in 1721 tests being run and 1 > skipped. So far, so good. > > However, if I run numpy.test(10,10,all=True), I get 1846 tests wi

[Numpy-discussion] test results of 1.2.0rc1

Hi, with numpy 1.2.0rc1 running 'python -c "import numpy; numpy.test()"' on my Ubuntu Hardy amd64 machine results in 1721 tests being run and 1 skipped. So far, so good. However, if I run numpy.test(10,10,all=True), I get 1846 tests with: the message "FAILED (SKIP=1, errors=8, failures=68)" Furthe

  1   2   >