On Fri, Aug 19, 2011 at 12:54 PM, Roberto De Ioris wrote:
>
> Il giorno 25/lug/2011, alle ore 14:31, Armin Rigo ha scritto:
>
>>
>> Indeed, there is nothing like that so far. We need to think out the
>> kind of C-level API which makes sense for libpypy.so to expose. There
>> are two options: eit
Il giorno 25/lug/2011, alle ore 14:31, Armin Rigo ha scritto:
>
> Indeed, there is nothing like that so far. We need to think out the
> kind of C-level API which makes sense for libpypy.so to expose. There
> are two options: either we tweak a little bit cpyext to expose the
> CPython C API, or
Armin Rigo, 25.07.2011 14:31:
On Mon, Jul 25, 2011 at 1:42 PM, Roberto De Ioris wrote:
We would like to start using PyPy, so our need is having a workable
libpypy.so implementation (we do not need it to be compatible with CPython
api, we can rewrite those parts, expecially in uWSGI, without prob
Hi,
2011/7/25 Roberto De Ioris
>
> Hi everyone, my company has a bunch of C apps (mainly the uWSGI
> application server container and a scriptable DNS server) embedding
> CPython in their core.
>
> We would like to start using PyPy, so our need is having a workable
> libpypy.so implementation (w
Hi Roberto,
On Mon, Jul 25, 2011 at 1:42 PM, Roberto De Ioris wrote:
> We would like to start using PyPy, so our need is having a workable
> libpypy.so implementation (we do not need it to be compatible with CPython
> api, we can rewrite those parts, expecially in uWSGI, without problems).
Indee
