cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
<cfbolz>
antocuni: sorry, I can't do that (kids still awake then)
dddddd has quit [Ping timeout: 272 seconds]
dddddd has joined #pypy
<wleslie>
it would not surprise me if serialisability was discarded in favour of something like the JMM soon
<arigato>
cfbolz : any time works for me for the call, if people want it to be a call
<cfbolz>
arigato: cool
_whitelogger has joined #pypy
* fijal
wants it to be a VR meeting
<fijal>
nascheme: I think part of the problem of removing GIL is that if pypy removed GIL it would have different semantics and it would be bad
<fijal>
we already had quite a few issues with pure-python code replacing C extensions (like bdb module) where atomicity guarantees are not documented but expected
<fijal>
so I think part of the problem is pretty bad concurrency story in python to start with
<fijal>
I would *also* say that doing part of that work (having some better story for C API) would pave the path for just in time compilation which is *definitely* faster, so maybe it can be spun that way