On Tue, Mar 27, 2012 at 21:55, Maciej Fijalkowski wrote:
Hi Maciej
>> do we really want to keep python 2.5 compat? It's not tested, and "what is
>> not
>> tested is broken"...
>
> There is no reason not to.
This version has reached end-of-life: no new version, even for major bugs.
--
Sebast
On Fri, Mar 23, 2012 at 1:13 AM, Lynne Wallace wrote:
> Hey everyone,
>
> I'm a 3rd year student at ed.ac.uk, interested in getting involved in pypy
> through google summer of code.
>
> I've been chatting to Alex Gaynor over irc - his primary suggestion was
> improving the register allocator.
> He
Well the reason not is that this has come up several times where someone
forgets a future import or something else.
Alex
On Tue, Mar 27, 2012 at 3:55 PM, Maciej Fijalkowski wrote:
> On Tue, Mar 27, 2012 at 9:36 PM, Antonio Cuni wrote:
> > Hi Armin,
> >
> > On 03/26/2012 01:31 PM, arigo wrote:
>
2012/3/27 Maciej Fijalkowski :
> There is no reason not to.
Is it useful for something?
--
Regards,
Benjamin
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
On Tue, Mar 27, 2012 at 9:36 PM, Antonio Cuni wrote:
> Hi Armin,
>
> On 03/26/2012 01:31 PM, arigo wrote:
>> Author: Armin Rigo
>> Branch:
>> Changeset: r53982:db33a634cb09
>> Date: 2012-03-26 13:16 +0200
>> http://bitbucket.org/pypy/pypy/changeset/db33a634cb09/
>>
>> Log: Python 2.5 compat
>
>
Hi Armin,
On 03/26/2012 01:31 PM, arigo wrote:
> Author: Armin Rigo
> Branch:
> Changeset: r53982:db33a634cb09
> Date: 2012-03-26 13:16 +0200
> http://bitbucket.org/pypy/pypy/changeset/db33a634cb09/
>
> Log: Python 2.5 compat
do we really want to keep python 2.5 compat? It's not tested, and "
On Tue, Mar 27, 2012 at 3:27 PM, Peter Cock wrote:
> On Wed, Mar 21, 2012 at 5:49 PM, Maciej Fijalkowski wrote:
>> On Wed, Mar 21, 2012 at 7:10 PM, Peter Cock
>> wrote:
>>> That doesn't sound quite so intimidating... and if I've understood this
>>> now it does seem like the basis of a good deve
On Wed, Mar 21, 2012 at 5:49 PM, Maciej Fijalkowski wrote:
> On Wed, Mar 21, 2012 at 7:10 PM, Peter Cock wrote:
>> That doesn't sound quite so intimidating... and if I've understood this
>> now it does seem like the basis of a good development FAQ entry:
>> http://doc.pypy.org/en/latest/faq.html#
Hi everyone, i have finally managed to have a pypy plugin into uWSGI via
libpypy-c.
The first step was exporting a bunch of symbols in libpypy-c:
"RPython_StartupCode", "pypy_g_ObjSpace_startup", "pypy_g_call_startup",
"pypy_g_State_startup", "pypy_g_Module_startup",
"pypy_g_pypy_module_cpyext_st
