cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake https://pypy.org | IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end and https://libera.irclog.whitequark.org/pypy | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
luckydonald has quit [Ping timeout: 256 seconds]
luckydonald has joined #pypy
jcea has joined #pypy
jcea has quit [Ping timeout: 246 seconds]
jcea has joined #pypy
jcea has quit [Ping timeout: 252 seconds]
otisolsen70 has joined #pypy
<mattip> pep 703 to make the GIL optional in pytohn 3.12 has been proposed, here is the preview
<mattip> actually quite readable, nice
<mattip> one part of the proposal is to use mimalloc
<mattip> it seems like it would be a good fit for the RPython GC too
<fijal> that's a complex incref/decref
<fijal> 5-10% seems very mellow, I wonder if it's true
<fijal> I think if people can agree what "python with no gil" means, it'll be much easier to do for us
<mattip> using a compile time switch and an ABI mark for c-extensions means that c-extension authors will have to opt-in to providing compatible wheels,
<mattip> which avoids a whole class of pain for c-extension authors who may not want to support no-gil
<arigato> reading https://pep-previews--2955.org.readthedocs.build/pep-0703/, I have doubts that it can be implemented completely reliably
<arigato> it talks about one thread modifying the reference count of an object while another thread frees it, and how to hack at the memory allocator to somehow make it work
<arigato> I cannot see how it can be made completely reliable, but then I don't know everything
jcea has joined #pypy
otisolsen70 has quit [Quit: Leaving]
dmalcolm has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
jcea has quit [Ping timeout: 260 seconds]
Julian has joined #pypy