[pypy-dev] release seems ready

Maciej Fijalkowski fijall at gmail.com
Tue Mar 8 10:11:56 EST 2016


ugh, btw, it seems someone broke embedding (as advertised, probably
the cffi embedding still works)

On Tue, Mar 8, 2016 at 4:53 PM, Maciej Fijalkowski <fijall at gmail.com> wrote:
> in other words, it shows the last release of pypy, not "trunk"
>
> On Tue, Mar 8, 2016 at 4:52 PM, Maciej Fijalkowski <fijall at gmail.com> wrote:
>> Cool, I'm happy to do the suggested fixes.
>>
>> We rerun it every release usually, changes by hand are done earlier.
>> Should I start a run on the current release branch?
>>
>> On Tue, Mar 8, 2016 at 4:46 PM, Armin Rigo <arigo at tunes.org> wrote:
>>> Hi,
>>>
>>> On 8 March 2016 at 15:42, Maciej Fijalkowski <fijall at gmail.com> wrote:
>>>> btw, should we mention packages.pypy.org?
>>>
>>> I would do so but only under two conditions:
>>>
>>> * it reports a post-cpyext-fixes result: which packages run or don't
>>> run now, ideally on the current "release 5.0" branch, but at least
>>> after the merge of the cpyext-gc-support-2 branch
>>>
>>> * we quickly review and fix the few manual comments, notably lxml's
>>> (we no longer recommend lxml-cffi).
>>>
>>>
>>> A bientôt,
>>>
>>> Armin


More information about the pypy-dev mailing list