[jira] [Commented] (PROTON-2095) Move away from SWIG to CFFI

["Jiri Daněk (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PROTON-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325666#comment-17325666 ] 

Jiri Daněk commented on PROTON-2095:
------------------------------------

h3. My CFFI references

[https://medium.com/paypal-tech/python-by-the-c-side-1f82fc94c4ad]

Some hints about Setuptools, [https://carsonip.me/posts/writing-a-python-wrapper-for-html2text-using-cffi/]

We want to use “out-of-line” + “API mode” CFFI with setuptools, [https://cffi.readthedocs.io/en/release-1.9/cdef.html]

Worked example for a relatively small C API [https://aldnav.com/blog/writing-a-geohash-wrapper-using-cffi/]

Python 3 strings [https://cffi.readthedocs.io/en/release-1.9/using.html?highlight=re#python-3-support]

Automatic generation of .pyi typing stub files [https://groups.google.com/g/python-cffi/c/6V8PBjA6ZJ4]

Slowest part of cffi seems to be processing the data in interpreted code, in and out (will be better in PyPy?) [https://blog.ian.stapletoncordas.co/2018/01/making-python-faster-with-rust-and-cffi-or-not.html]

More perf, Cython vs cffi [https://zpz.github.io/blog/speeding-up-python-with-c-and-cffi/]

> Move away from SWIG to CFFI
> ---------------------------
>
>                 Key: PROTON-2095
>                 URL: https://issues.apache.org/jira/browse/PROTON-2095
>             Project: Qpid Proton
>          Issue Type: Wish
>          Components: python-binding
>    Affects Versions: proton-c-future, proton-c-0.29.0
>            Reporter: Omer Katz
>            Priority: Major
>             Fix For: proton-c-future
>
>
> SWIG is fine but we're not using it for anything other than exporting all of proton-c's API as is.
> Unfortunately SWIG only generates CPython extension bindings. This may be a problem on PyPy where CPython extensions are either slow or simply won't compile.
> Unlike SWIG, CFFI is portable both on CPython and PyPy.
> It also satisfies the same requirements as SWIG currently does.
> In addition, calls to CFFI simply release the GIL which will help parallelizing Python applications using threads.
> By using CFFI we can also get rid of all of our setup.py code and simply use it to build the extension. We will also no longer have problems building wheels.
> The newest version of CFFI supports pkg-config so we can use that to find proton-c easily.
> I'm willing to help with the refactor but I'll need a mentor since I'm not familiar with the code base.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org