From 72c9eea9e58f9b57f97a32a3ab9e3ca9b25dd736 Mon Sep 17 00:00:00 2001 From: Pauli Virtanen Date: Sat, 10 Oct 2009 16:12:27 +0000 Subject: Don't include assert_valid_refcount in numpy.testing.* It's a private function used only in two internal regression tests. --- numpy/testing/utils.py | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'numpy/testing/utils.py') diff --git a/numpy/testing/utils.py b/numpy/testing/utils.py index 71b5944b6..e5e86250f 100644 --- a/numpy/testing/utils.py +++ b/numpy/testing/utils.py @@ -14,7 +14,7 @@ __all__ = ['assert_equal', 'assert_almost_equal','assert_approx_equal', 'assert_array_almost_equal', 'assert_raises', 'build_err_msg', 'decorate_methods', 'jiffies', 'memusage', 'print_assert_equal', 'raises', 'rand', 'rundocs', 'runstring', 'verbose', 'measure', - 'assert_', 'assert_valid_refcount'] + 'assert_'] verbose = 0 @@ -1064,7 +1064,11 @@ def measure(code_str,times=1,label=None): elapsed = jiffies() - elapsed return 0.01*elapsed -def assert_valid_refcount(op): +def _assert_valid_refcount(op): + """ + Check that ufuncs don't mishandle refcount of object `1`. + Used in a few regression tests. + """ import numpy as np a = np.arange(100 * 100) b = np.arange(100*100).reshape(100, 100) -- cgit v1.2.1