Author: Armin Rigo <[email protected]> Branch: Changeset: r68374:f7b797f79170 Date: 2013-12-04 15:58 +0100 http://bitbucket.org/pypy/pypy/changeset/f7b797f79170/
Log: Move this doc into its proper place and expand a bit. diff --git a/pypy/doc/cpython_differences.rst b/pypy/doc/cpython_differences.rst --- a/pypy/doc/cpython_differences.rst +++ b/pypy/doc/cpython_differences.rst @@ -316,9 +316,4 @@ type and vice versa. For builtin types, a dictionary will be returned that cannot be changed (but still looks and behaves like a normal dictionary). -* ``ctypes.pythonapi`` lets you access the CPython C API emulation layer - of PyPy, at your own risks and without doing anything sensible about - e.g. the GIL. Since PyPy 2.3, the functions are called with an extra - "Py", for example ``PyPyInt_FromLong()``. - .. include:: _ref.txt diff --git a/pypy/doc/ctypes-implementation.rst b/pypy/doc/ctypes-implementation.rst --- a/pypy/doc/ctypes-implementation.rst +++ b/pypy/doc/ctypes-implementation.rst @@ -72,7 +72,13 @@ Here is a list of the limitations and missing features of the current implementation: -* No support for ``PyXxx`` functions from ``libpython``, for obvious reasons. +* ``ctypes.pythonapi`` lets you access the CPython C API emulation layer + of PyPy, at your own risks and without doing anything sensible about + the GIL. Since PyPy 2.3, these functions are also named with an extra + "Py", for example ``PyPyInt_FromLong()``. Basically, don't use this, + but it might more or less work in simple cases if you do. (Obviously, + assuming the PyObject pointers you get have any particular fields in + any particular order is just going to crash.) * We copy Python strings instead of having pointers to raw buffers _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
