[pypy-dev] merging pypy-pyarray branch

Matti Picus matti.picus at gmail.com
Mon Sep 23 15:05:22 CEST 2013


On 09/23/2013 04:01 PM, Romain Guillebert wrote:
> Hi Matti
>
> +1 for me.
>
> On Mon, Sep 23, 2013 at 11:16 AM, Maciej Fijalkowski <fijall at gmail.com> wrote:
>> On Sun, Sep 22, 2013 at 5:26 PM, Matti Picus <matti.picus at gmail.com> wrote:
>>> I am getting close to being ready to merge the pypy-pyarray branch. I
>>> related to all the review items from
>>> https://bitbucket.org/pypy/pypy/src/1a379a6f127bd6df8a4b628575c7124e83007e60/TODO.txt
>>> <https://bitbucket.org/pypy/pypy/src/1a379a6f127bd6df8a4b628575c7124e83007e60/TODO.txt?at=pypy-pyarray>
>>> Does anyone have objections to merging pypy-pyarray into default (assuming
>>> the buildbots come up with no failures)?
>>>
>>> Executive summary - I took over Stefan__'s work to implement the c api
>>> interface from numpy. This together with a fork of numpy and a fork of
>>> matplotlib got him to a point where he could use non-interpretive plotting
>>> (png, pdf) in matplotlib.
>>> Matti
>>> _______________________________________________
>>> pypy-dev mailing list
>>> pypy-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pypy-dev
>> I would say "go ahead"
>> _______________________________________________
>> pypy-dev mailing list
>> pypy-dev at python.org
>> https://mail.python.org/mailman/listinfo/pypy-dev
Done. I ran a test build, which came up clean Yay! Thanks, Stefan


More information about the pypy-dev mailing list