<div class="gmail_quote"><div>Hi Armin</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I would say that in this case, keeping your module in C with a<br>
C-friendly API is the most future-proof solution I can think of. That<br>
means so far --- with today's tools --- that you need to wrap it<br>
twice, as a CPython C extension module and as a pure Python ctypes, in<br>
order to get good performance on both CPython and PyPy.<br></blockquote><div><br></div><div>Thanks, that's a very helpful conclusion and actually a perfectly workable solution for now. I will keep a close eye on the blog for future developments in this area, and I certainly hope that I will be able to make the switch soon.</div>
<div><br></div><div>Let me just tie this up by thanking you all for your extensive and very helpful replies. It's been a very enlightening discussion.</div><div><br></div><div>Much obliged,</div><div><br></div><div>Gertjan</div>
</div>