diff options
author | Charles Harris <charlesr.harris@gmail.com> | 2014-03-14 11:57:45 -0600 |
---|---|---|
committer | Charles Harris <charlesr.harris@gmail.com> | 2014-03-14 11:57:45 -0600 |
commit | 17227ce130cae09f03c55df1ed22798be901c7ff (patch) | |
tree | 95d54c2b90c71c0c932798be602215c404c00f0b | |
parent | 8eb120fd13c50b269bb752a4dd5207c1fba9c905 (diff) | |
parent | a2ca82f0b145e0e5f6c051259bd0df4ea1b87127 (diff) | |
download | numpy-17227ce130cae09f03c55df1ed22798be901c7ff.tar.gz |
Merge pull request #4493 from charris/reference-cython-not-pyrex
DOC: Change pyrex to Cython in c-info.how-to-extend.rst.
-rw-r--r-- | doc/source/user/c-info.how-to-extend.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/user/c-info.how-to-extend.rst b/doc/source/user/c-info.how-to-extend.rst index 5901ce3e3..db6c8e118 100644 --- a/doc/source/user/c-info.how-to-extend.rst +++ b/doc/source/user/c-info.how-to-extend.rst @@ -255,7 +255,7 @@ Reference counting The biggest difficulty when writing extension modules is reference counting. It is an important reason for the popularity of f2py, weave, -pyrex, ctypes, etc.... If you mis-handle reference counts you can get +Cython, ctypes, etc.... If you mis-handle reference counts you can get problems from memory-leaks to segmentation faults. The only strategy I know of to handle reference counts correctly is blood, sweat, and tears. First, you force it into your head that every Python variable |