Author: Armin Rigo <[email protected]> Branch: Changeset: r69129:979a9e29354f Date: 2014-02-13 19:37 +0100 http://bitbucket.org/pypy/pypy/changeset/979a9e29354f/
Log: Update ''Embedding PyPy'' diff --git a/pypy/doc/project-ideas.rst b/pypy/doc/project-ideas.rst --- a/pypy/doc/project-ideas.rst +++ b/pypy/doc/project-ideas.rst @@ -148,12 +148,11 @@ Note: there is a basic proof-of-concept for that as a `uwsgi pypy plugin`_ Being able to embed PyPy, say with its own limited C API, would be -useful. But here is the most interesting variant, straight from -EuroPython live discussion :-) We can have a generic "libpypy.so" that -can be used as a placeholder dynamic library, and when it gets loaded, -it runs a .py module that installs (via ctypes) the interface it wants -exported. This would give us a one-size-fits-all generic .so file to be -imported by any application that wants to load .so files :-) +useful. But there is a possibly better variant: use CFFI. With some +minimal tools atop CFFI, it would be possible to write a pure Python +library, and then compile automatically from it an .so/.dll file that is +a dynamic-link library with whatever C API we want. This gives us a +one-size-fits-all generic way to make .so/.dll files from Python. .. _`uwsgi pypy plugin`: http://uwsgi-docs.readthedocs.org/en/latest/PyPy.html _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
