[Numpy-discussion] Test

This is a test to see if the list is working for me. -teo ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

[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

[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

[Numpy-discussion] test issue

Hello, I've been going thru Dave Kuhlman's "SciPy Course Outline" (http:// www.rexx.com/~dkuhlman/scipy_course_01.html) and found out about test functions -- very cool. Except that on my end, not all tests pass (appended below). Is this a problem for other people? Is it something I should w

[Numpy-discussion] test issue

Hello, I've been going thru Dave Kuhlman's "SciPy Course Outline" and found out about test functions -- very cool. Except that on my end, not all tests pass (appended below). Is this a problem for other people? Is it something I should worry about? Here's my setup: Mac G5 w/OS X 10.4.8, usi

[Numpy-discussion] test failures

Hi Stefan, I believe these come from your latest commit. File "/usr/lib/python2.5/site-packages/numpy/lib/tests/test_ufunclike.py", line 25, in test_ufunclike Failed example: nx.sign(a) Expected: array([ 1., -1., 0., 0., 1., -1.]) Got: array([ 1., -1., -1., 0., 1., -1.])

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

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()

[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

[Numpy-discussion] Test from work

This is a test -teo ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Test framework changes

Hi all, Just wanted to get feedback about the following changes before I make them. Please speak up if any of this seems objectionable to you. - The old test framework classes will be restored, but will not be used anywhere in NumPy's tests. If your old tests still don't work with the restored

Re: [Numpy-discussion] test issue

belinda thom wrote: > Hello, > > I've been going thru Dave Kuhlman's "SciPy Course Outline" (http:// > www.rexx.com/~dkuhlman/scipy_course_01.html) and found out about test > functions -- very cool. Except that on my end, not all tests pass > (appended below). Is this a problem for other peop

Re: [Numpy-discussion] test issue

Eric, Thanks for the well-thought-out answers to some of my recent posts. I've been using: http://pythonmac.org/packages/py24-fat/index.html for installing scipy, numpy, and matplotlib, as I didn't feel as confident installing things manually. Should I be using svn instead? (Is that what mos

Re: [Numpy-discussion] test issue

belinda thom wrote: > Eric, > > Thanks for the well-thought-out answers to some of my recent posts. > > I've been using: > > http://pythonmac.org/packages/py24-fat/index.html > > for installing scipy, numpy, and matplotlib, as I didn't feel as > confident installing things manually. > > Shou

Re: [Numpy-discussion] test issue

Thanks again for the input. You've been really helpful. On Dec 29, 2006, at 8:47 PM, Eric Firing wrote: > As far as I know, your pythonmac package > source is a good choice. I'm sure one of the many Mac users on this > list can elaborate. I won't go into the long tirade of problems I've run in

Re: [Numpy-discussion] test failures

Hi Charles On Wed, Feb 13, 2008 at 03:39:53PM -0700, Charles R Harris wrote: > I believe these come from your latest commit. My changeset is here: http://projects.scipy.org/scipy/numpy/changeset/4800 I don't see how that would have broken the tests you listed. Regards Stéfan __

Re: [Numpy-discussion] test failures

On Thu, Feb 14, 2008 at 2:01 AM, Stefan van der Walt <[EMAIL PROTECTED]> wrote: > Hi Charles > > On Wed, Feb 13, 2008 at 03:39:53PM -0700, Charles R Harris wrote: > > I believe these come from your latest commit. > > My changeset is here: > > http://projects.scipy.org/scipy/numpy/changeset/4800 >

[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 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

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 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 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

[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 framework changes

On Fri, Jun 20, 2008 at 16:01, Alan McIntyre <[EMAIL PROTECTED]> wrote: > - numpy.test now returns an object with a wasSuccessful method; under > the old test framework it returned a unittest._TextTestResult, but > since nose.run only returns success/failure, I'm just wrapping this > result in a d

Re: [Numpy-discussion] Test framework changes

On Fri, Jun 20, 2008 at 5:35 PM, Robert Kern <[EMAIL PROTECTED]> wrote: > So NoseTester.run() basically just calls nose.run(). That basically > just instantiates nose.core.TestProgram and returns the .success > attribute of it. Unfortunately, the TextTestResults object (a nose > subclass of unittes

Re: [Numpy-discussion] Test framework changes

On Fri, Jun 20, 2008 at 3:04 PM, Alan McIntyre <[EMAIL PROTECTED]> wrote: > On Fri, Jun 20, 2008 at 5:35 PM, Robert Kern <[EMAIL PROTECTED]> wrote: >> So NoseTester.run() basically just calls nose.run(). That basically >> just instantiates nose.core.TestProgram and returns the .success >> attribute

Re: [Numpy-discussion] Test framework changes

On Fri, Jun 20, 2008 at 7:22 PM, Fernando Perez <[EMAIL PROTECTED]> wrote: > It may be worth bringing it up wtih the nose guys here: > > http://lists.idyll.org/listinfo/testing-in-python > > The nose author seems very responsive, and Titus Brown is on the list > and cares a lot about numpy/scipy, a

Re: [Numpy-discussion] Test framework changes

On Fri, Jun 20, 2008 at 6:22 PM, Alan McIntyre <[EMAIL PROTECTED]> wrote: > On Fri, Jun 20, 2008 at 7:22 PM, Fernando Perez <[EMAIL PROTECTED]> > wrote: > > It may be worth bringing it up wtih the nose guys here: > > > > http://lists.idyll.org/listinfo/testing-in-python > > > > The nose author see

Re: [Numpy-discussion] Test framework changes

These changes are now checked in, with the changes Robert suggested: numpy.test() returns a TextTestResult object again, and coverage (if enabled) is limited to the package from which test is called. The tests still fail because the buildbots don't have nose installed, though. On Fri, Jun 20, 200

[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

[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 ..

[Numpy-discussion] test failure: Ticket 396

Hello, Just thought I'd report this test failure with current svn (rev 4464) on Mac OS X 10.5 (could be a leopard issue?) since I hadn't seen it mentioned before. Oddly it only seems to fail in ipython, importing and running from the normal python interpreter all the tests pass. Actually, it only

[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

[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

[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 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 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

[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 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 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:

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 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

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

[Numpy-discussion] Test Faliures on OS-X

HI all, I missed a bit of the release process, but I thought all the test failures had been squashed. However, I just installed the OS-X 1.1.0 binary, and got: >>> import numpy >>> numpy.__version__ '1.1.0' >>> >>> from numpy import test >>> test(all=True) Numpy is installed in /Library/F

[Numpy-discussion] test errors with numpy-1.1.0

On an AMD x86_64 with ATLAS installed I am getting errors like ValueError: On entry to DLASD0 parameter number 9 had an illegal value ValueError: On entry to ILAENV parameter number 2 had an illegal value Anybody seen this before? Mathew ___ Numpy-di

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

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

[Numpy-discussion] Test failure with latest SVN

I am on OS X 10.5.1 and get a test failure with the latest numpy svn. (Previously ran with no errors with svn as of a few weeks ago). test_zero_probability (numpy.tests.test_random.TestMultinomial) ... ok == ERROR: Ticket #396 --

[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 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

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 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 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

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

> 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 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

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 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

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

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 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/

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

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 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: > > 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: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 Faliures on OS-X

Pierre GM wrote: > Mmh, there's something wrong in your installation: there shouldn't be any > ma.py file in numpy.core, nor test_ma.py in in numpy/core/tests. OK, I'll do a clean-up and try again. this is probably due to having previously installed a release candidate a while back... Bingo!:

Re: [Numpy-discussion] Test Faliures on OS-X

On Monday 02 June 2008 13:46:42 Christopher Barker wrote: > HI all, > > I missed a bit of the release process, but I thought all the test > failures had been squashed. However, I just installed the OS-X 1.1.0 > binary, and got: > >>> import numpy > >>> numpy.__version__ Mmh, there's something wr

Re: [Numpy-discussion] test errors with numpy-1.1.0

On Wed, Aug 13, 2008 at 7:11 PM, Mathew Yeates <[EMAIL PROTECTED]> wrote: > On an AMD x86_64 with ATLAS installed I am getting errors like > ValueError: On entry to DLASD0 parameter number 9 had an illegal value > ValueError: On entry to ILAENV parameter number 2 had an illegal value Which platfor

Re: [Numpy-discussion] Test failure with latest SVN

I just built from svn in Ubuntu and get this same error. Ryan On Jan 16, 2008 5:26 AM, Robin <[EMAIL PROTECTED]> wrote: > I am on OS X 10.5.1 and get a test failure with the latest numpy svn. > (Previously ran with no errors with svn as of a few weeks ago). > > test_zero_probability (numpy.tests.

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

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

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

[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

[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 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

[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 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 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

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?

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?

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 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 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 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: > >

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 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, 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

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, 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

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

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

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 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 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 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

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

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 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 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

  1   2   >