Re: DRAFT Introduce CFFI-based Python bindings

On Wed, Nov 29 2017, Floris Bruynooghe wrote: > David Bremner writes: > >> Floris Bruynooghe writes: >> >>> >>> Lastly there are some downsides to the choices I made: >>> - I ended up going squarely for CPython 3.6+. Choosing Python >>> 3 allowed better API

Re: DRAFT Introduce CFFI-based Python bindings

Florian Klink writes: >>> I guess you'll have to convince the maintainers / users of alot and afew >>> that this makes sense before we go much further. I'd point out that >>> Debian stable is only at python 3.5, so that makes me a bit wary of this >>> (being able to run the

Re: DRAFT Introduce CFFI-based Python bindings

I guess you'll have to convince the maintainers / users of alot and afew that this makes sense before we go much further. I'd point out that Debian stable is only at python 3.5, so that makes me a bit wary of this (being able to run the test suite on debian stable and similar aged distros useful

Re: DRAFT Introduce CFFI-based Python bindings

Patrick Totzke writes: > Quoting David Bremner (2017-11-28 23:59:26) >> Floris Bruynooghe writes: >> >> > >> > Lastly there are some downsides to the choices I made: >> > - I ended up going squarely for CPython 3.6+. Choosing Python >> > 3 allowed

Re: DRAFT Introduce CFFI-based Python bindings

David Bremner writes: > Floris Bruynooghe writes: > >> >> Lastly there are some downsides to the choices I made: >> - I ended up going squarely for CPython 3.6+. Choosing Python >> 3 allowed better API design, e.g. with keyword-only parameters >> etc.

Re: DRAFT Introduce CFFI-based Python bindings

Quoting David Bremner (2017-11-28 23:59:26) > Floris Bruynooghe writes: > > > > > Lastly there are some downsides to the choices I made: > > - I ended up going squarely for CPython 3.6+. Choosing Python > > 3 allowed better API design, e.g. with keyword-only parameters > >

Re: DRAFT Introduce CFFI-based Python bindings

Floris Bruynooghe writes: > > Lastly there are some downsides to the choices I made: > - I ended up going squarely for CPython 3.6+. Choosing Python > 3 allowed better API design, e.g. with keyword-only parameters > etc. Choosing CPython 3.4+ restricts the madness that can

DRAFT Introduce CFFI-based Python bindings

Hi all, Here are the beginnings off CFFI-based Python bindings, rather than the ctypes-based ones currently available. I started this work in order to get faster bindings on pypy since a script of mine was running slower on pypy than CPython. Initially aiming for a drop-in replacement of the