diff options
author | Travis Oliphant <oliphant@enthought.com> | 2006-07-06 16:55:18 +0000 |
---|---|---|
committer | Travis Oliphant <oliphant@enthought.com> | 2006-07-06 16:55:18 +0000 |
commit | 216f071ab060a6f08c22666aea33f7095f079d1e (patch) | |
tree | 9d70df14a55d99d9e09db00cc1e3c2c02ce786b8 /numpy/doc/pyrex/numpyx.pyx | |
parent | fb83db13965023c3f82eef0cf1b8e8b18789f5b9 (diff) | |
download | numpy-216f071ab060a6f08c22666aea33f7095f079d1e.tar.gz |
Fix UserArray.
Diffstat (limited to 'numpy/doc/pyrex/numpyx.pyx')
-rw-r--r-- | numpy/doc/pyrex/numpyx.pyx | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/numpy/doc/pyrex/numpyx.pyx b/numpy/doc/pyrex/numpyx.pyx index 4cd6dbd29..8089fbc38 100644 --- a/numpy/doc/pyrex/numpyx.pyx +++ b/numpy/doc/pyrex/numpyx.pyx @@ -63,8 +63,8 @@ def test_methods(c_numpy.ndarray arr): This illustrates how the pyrex-visible object is in practice a strange hybrid of the C PyArrayObject struct and the python object. Some properties (like .nd) are visible here but not in python, while others - like flags behave very differently: in python flags appears as a dict, - while here we see the raw int holding the bit pattern. + like flags behave very differently: in python flags appears as a separate, + object while here we see the raw int holding the bit pattern. This makes sense when we think of how pyrex resolves arr.foo: if foo is listed as a field in the c_numpy.ndarray struct description, it will be @@ -81,10 +81,10 @@ def test_methods(c_numpy.ndarray arr): def test(): """this function is pure Python""" - arr1 = numpy.array(-1e-30,dtype=numpy.Float64) - arr2 = numpy.array([1.0,2.0,3.0],dtype=numpy.Float64) + arr1 = numpy.array(-1e-30,dtype=numpy.float64) + arr2 = numpy.array([1.0,2.0,3.0],dtype=numpy.float64) - arr3 = numpy.arange(9,dtype=numpy.Float64) + arr3 = numpy.arange(9,dtype=numpy.float64) arr3.shape = 3,3 four = 4 |