How is python 3.4 release coming?.
On Fri, Aug 21, 2015 at 3:08 AM, Maciej Fijalkowski
wrote:
> On Thu, Aug 20, 2015 at 9:31 PM, Matti Picus
> wrote:
> > On 19/08/15 22:54, Maciej Fijalkowski wrote:
> >>
> >> I fixed a few bugs, I will write a parser for vmmap tomorrow
> >> Maciej Fijalkowski
>
On Thu, Aug 20, 2015 at 9:31 PM, Matti Picus wrote:
> On 19/08/15 22:54, Maciej Fijalkowski wrote:
>>
>> I fixed a few bugs, I will write a parser for vmmap tomorrow
>> Maciej Fijalkowski
>
>
> Will the vmmap parser be part of pypy, and if so are you requesting I wait
> with 2.6.1 until it is read
On Wednesday, 19 August 2015 21:36:37 Matti Picus wrote:
> I have started the release cycle for 2.6.1, are there outstanding issues
> or soon-to-be-committed features I should wait for?
Hi Matti,
It would be great if the patch from issue #2107 could be committed. The patch
has been compile test
On 19/08/15 22:54, Maciej Fijalkowski wrote:
I fixed a few bugs, I will write a parser for vmmap tomorrow
Maciej Fijalkowski
Will the vmmap parser be part of pypy, and if so are you requesting I
wait with 2.6.1 until it is ready?
Matti
___
pypy-dev
Hi Matti,
On 19 August 2015 at 20:36, Matti Picus wrote:
> Please help with the release notice, what have we done since 2.6.0 or at
> all?
The stdlib is now 2.7.10 and cffi is 1.2.
I think the most interesting change is int-float-list-strategy, at
least in terms of explaining it:
"""Use a comp
Hi Matti,
On 20 August 2015 at 00:01, Matti Picus wrote:
> P.S. - an alternative would be to override the hg update mechanism so the
> repos do not get out of sync, perhaps that will be easier.
Alternatively, we should check out the out-of-sync repo. It's likely
because it has custom commits in
