Re: [Python-Dev] CFFI released

2012-06-19 Thread Armin Rigo
Hi Stefan, On Tue, Jun 19, 2012 at 8:28 AM, Stefan Behnel wrote: > Any reason you didn't write the C parts in Cython? '''As a general rule, when there is a design issue to resolve, we pick the solution that is the “most C-like”.''' (from the documentation). But you are welcome to write Cython bi

Re: [Python-Dev] CFFI released

2012-06-19 Thread Armin Rigo
Hi Greg, On Tue, Jun 19, 2012 at 8:30 AM, Greg Ewing wrote: > Is there any provision for keeping the compiled > C code and distributing it along with an application? > Requiring a C compiler to be present at all times > could be a difficulty for Windows. We are aware of it and doing that is work

Re: [Python-Dev] CFFI released

2012-06-18 Thread Greg Ewing
Is there any provision for keeping the compiled C code and distributing it along with an application? Requiring a C compiler to be present at all times could be a difficulty for Windows. -- Greg ___ Python-Dev mailing list Python-Dev@python.org http://m

Re: [Python-Dev] CFFI released

2012-06-18 Thread Stefan Behnel
Armin Rigo, 18.06.2012 23:29: > On Mon, Jun 18, 2012 at 9:10 PM, Maciej Fijalkowski wrote: >>> Make cffi less buggy (check the tracker for new test cases ;-), faster >>> (closer to swig type wrappers), and easier to use than ctypes, and I am sure >>> there will be interest. >> >> I would say it's a

Re: [Python-Dev] CFFI released

2012-06-18 Thread Nick Coghlan
On Tue, Jun 19, 2012 at 12:35 PM, Terry Reedy wrote: > Yes, because languages have no speed, only implementations do; and yes, > because when CPython really is too slow for a particular task, it can be > pushed onto C. But some people (pygame, others on python-list) have reported > that for their

Re: [Python-Dev] CFFI released

2012-06-18 Thread Terry Reedy
On 6/18/2012 5:29 PM, Armin Rigo wrote: On Mon, Jun 18, 2012 at 9:10 PM, Maciej Fijalkowski wrote: >> Me Make cffi less buggy (check the tracker for new test cases ;-), faster (closer to swig type wrappers), and easier to use than ctypes, and I am sure there will be interest. I would say it'

Re: [Python-Dev] CFFI released

2012-06-18 Thread Armin Rigo
Hi, On Mon, Jun 18, 2012 at 9:10 PM, Maciej Fijalkowski wrote: >> Make cffi less buggy (check the tracker for new test cases ;-), faster >> (closer to swig type wrappers), and easier to use than ctypes, and I am sure >> there will be interest. > > I would say it's already fulfilling those three,

Re: [Python-Dev] CFFI released

2012-06-18 Thread Maciej Fijalkowski
On Mon, Jun 18, 2012 at 7:02 PM, Terry Reedy wrote: > On 6/18/2012 9:14 AM, Armin Rigo wrote: > >> Hi all, >> >> We (=fijal and myself) finally released the beta-0.1 version of CFFI. >> >> http://cffi.readthedocs.org/ >> >> It is a(nother) simple Foreign Function Interface for Python calling C >>

Re: [Python-Dev] CFFI released

2012-06-18 Thread Terry Reedy
On 6/18/2012 9:14 AM, Armin Rigo wrote: Hi all, We (=fijal and myself) finally released the beta-0.1 version of CFFI. http://cffi.readthedocs.org/ It is a(nother) simple Foreign Function Interface for Python calling C code. I talked about it with a few python core people during the PyCon spri

[Python-Dev] CFFI released

2012-06-18 Thread Armin Rigo
Hi all, We (=fijal and myself) finally released the beta-0.1 version of CFFI. http://cffi.readthedocs.org/ It is a(nother) simple Foreign Function Interface for Python calling C code. I talked about it with a few python core people during the PyCon sprint; now it's done, with a pure Python part