Re: [pypy-dev] Separate compilation and friends

2011-02-16 Thread Michael Foord
On 15 February 2011 01:13, Maciej Fijalkowski wrote: > Hi. > > There is growing interest about PyPy and especially about extension > modules. Apparently there are some people (like Alex) that are willing > to write modules in RPython that should not go to the main tree. As a side note I think

Re: [pypy-dev] Separate compilation and friends

2011-02-16 Thread William ML Leslie
On 15 February 2011 12:13, Maciej Fijalkowski wrote: > Hi. > > There is growing interest about PyPy and especially about extension > modules. Apparently there are some people (like Alex) that are willing > to write modules in RPython that should not go to the main tree. Since > separate compilatio

Re: [pypy-dev] Separate compilation and friends

2011-02-15 Thread Dima Tisnek
On 15 February 2011 01:32, Paolo Giarrusso wrote: > On Tue, Feb 15, 2011 at 09:17, Dima Tisnek wrote: >> On 15 February 2011 01:10, Antonio Cuni wrote: >>> On 15/02/11 03:41, Dima Tisnek wrote: On a related note, how hard is it to "freeze" the translator/compiler state of a given pypy

Re: [pypy-dev] Separate compilation and friends

2011-02-15 Thread Paolo Giarrusso
On Tue, Feb 15, 2011 at 09:17, Dima Tisnek wrote: > On 15 February 2011 01:10, Antonio Cuni wrote: >> On 15/02/11 03:41, Dima Tisnek wrote: >>> On a related note, how hard is it to "freeze" the translator/compiler >>> state of a given pypy version just before it begins to read extension >>> modul

Re: [pypy-dev] Separate compilation and friends

2011-02-15 Thread Paolo Giarrusso
On Tue, Feb 15, 2011 at 09:10, Antonio Cuni wrote: > On 15/02/11 03:41, Dima Tisnek wrote: >> On a related note, how hard is it to "freeze" the translator/compiler >> state of a given pypy version just before it begins to read extension >> modules and distribute that, it would speed up module deve

Re: [pypy-dev] Separate compilation and friends

2011-02-15 Thread Dima Tisnek
On 15 February 2011 01:10, Antonio Cuni wrote: > On 15/02/11 03:41, Dima Tisnek wrote: >> On a related note, how hard is it to "freeze" the translator/compiler >> state of a given pypy version just before it begins to read extension >> modules and distribute that, it would speed up module developm

Re: [pypy-dev] Separate compilation and friends

2011-02-15 Thread Antonio Cuni
On 15/02/11 03:41, Dima Tisnek wrote: > On a related note, how hard is it to "freeze" the translator/compiler > state of a given pypy version just before it begins to read extension > modules and distribute that, it would speed up module development a > lot. > It would be a quick equivalent of dist

Re: [pypy-dev] Separate compilation and friends

2011-02-14 Thread William ML Leslie
On 15 February 2011 12:13, Maciej Fijalkowski wrote: > Hi. > > There is growing interest about PyPy and especially about extension > modules. Apparently there are some people (like Alex) that are willing > to write modules in RPython that should not go to the main tree. Since > separate compilatio

Re: [pypy-dev] Separate compilation and friends

2011-02-14 Thread Dima Tisnek
On a related note, how hard is it to "freeze" the translator/compiler state of a given pypy version just before it begins to read extension modules and distribute that, it would speed up module development a lot. It would be a quick equivalent of distributing headers for a C library. d. On 14 Feb

[pypy-dev] Separate compilation and friends

2011-02-14 Thread Maciej Fijalkowski
Hi. There is growing interest about PyPy and especially about extension modules. Apparently there are some people (like Alex) that are willing to write modules in RPython that should not go to the main tree. Since separate compilation is considered hard, how hard would it be to provide separate lo