Hey everyone!
Those of you who attended or followed one of the last two winter sprints
in Leysin might know me, the others probably won't. I'm (still) a
Master's student writing my thesis on PyPy's current issue with
cross-heap cycles when using cpyext. The main point is, that they are
not collected and stay around as floating garbage, even if they are not
reachable any more. Correct me if I'm wrong, but I didn't notice anyone
else working on that topic (and/or committing something) since I've
picked it up two years ago (yeah, I know, that long ago...).
I saw that you would be working on "cpyext performance and completeness"
during the current winter sprint this week and thought that this might
also concern my thesis. So I thought I'll give you an update.
I recently pushed my current (non-optimized, breaking-some-tests, but
more or less working) implementation of the "CPython-style" GC-extension
for cpyext. It is still in an early stage and not all cases (legacy and
non-legacy-finalizers, weakrefs) are handled. However, I picked up some
pace during the last couple of weeks and I'm determined to finish this
implementation during the following weeks (some quirks with the tests
have been haunting me, but I think I figured most of them out by now).
After that, I will implement a second alternative implementation (to
compare to, mostly for the sake of my thesis), which will take some more
time. I also added a couple of fancy test cases (the so called
"dot-tests"), so that we can test complex object graphs a little bit
easier (and also because it was kind of cool to have another language
inside PyPy/RPython, even if it was only for the tests...), with more
test cases to come (the current ones are a bit messy). None of the new
changes concerning low-latency applications are currently integrated,
but that should not be too hard.
I guess it won't make much sense for me to join you at this year's
winter sprint, especially as I won't be able to get there before
Thursday, but I might be able to join you over the IRC channel (or some
other form of communication if you like). If there is anything that is
worth discussing please let me know! Also feel free to comment on my
code, but beware that I might change some things once I try to do some
optimizations (probably not many, but at least fix the worst issues) and
make it a little bit more readable. You can find my code on the
cpyext-gc-cycle
branch.<https://bitbucket.org/pypy/pypy/commits/branch/cpyext-gc-cycle>
Looking forward to hearing from you!
Greetings,
Stefan
Hi,
I think it would be a good idea to make squeaky's portable pypy builds [1]
more official by moving the repo to something like github.com/pypy/portable.
I think it's a good idea for various reasons, in particular:
1. we already link them from pypy.org, although not very prominently
2. they are used as a base for my manylinux-pypy docker image [2], which
I'd like to become "the official way to build PyPy wheels" (and thus move
it to something like github.com/pypy/manylinux or so).
[1] https://github.com/squeaky-pl/portable-pypy
[2] https://travis-ci.org/antocuni/manylinux-pypy
Does anybody have opinions on this?
Hi Pierre-Yves, hi all,
Here's a forwarded announcement for the upcoming Mercurial sprint in
Paris. None of us also involved in Baroque Software can be there
because the date conflicts with another conference we're taking part
in. But other people could be interested.
A bientôt,
Armin.
---------- Forwarded message ---------
From: Pierre-Yves David <pierre-yves.david(a)octobus.net>
Date: Mon, 6 May 2019 at 16:28
Subject: Mercurial conference Paris end of May
To: Armin Rigo <arigo(a)baroquesoftware.com>, Maciej Fijalkowski
<fijal(a)baroquesoftware.com>, georges Racinet
<georges.racinet(a)octobus.net>
Hey Baroque Software,
I wanted to make sure you are aware of the upcoming Mercurial Conference
in Paris (France) at the end of May (28th). It will gather users from
diverse backgrounds to share experiences, exchange with core developers
and discover new features.
The first edition will focus in particular on modern tooling, workflows
and scaling. We would be very happy to have some someone from Baroque
and the Pypy project with us.
Free free to forward the information to the pypy project. I am not sure
about the best way for me to do it.
You can read more details in the original announcement :
https://www.mercurial-scm.org/pipermail/mercurial/2019-April/051196.html
And registration is available here:
https://www.weezevent.com/mercurial-conference-paris-2019.
Cheers,
--
Pierre-Yves David
