otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #pypy
lritter has joined #pypy
tumbleweed_ has quit [Quit: Changing server]
tumbleweed has joined #pypy
Dejan has joined #pypy
slav0nic has joined #pypy
j4at has joined #pypy
lritter has quit [Ping timeout: 268 seconds]
j4at has quit []
Dejan has quit [Quit: Leaving]
Dejan has joined #pypy
slav0nic has quit [Ping timeout: 268 seconds]
derpydoo has joined #pypy
<mattip>
in hpy debug mode, the handles that are closed somehow keep the object alive
<mattip>
I tried to do something in d9d67ee5a28b but that is wrong
<mattip>
I am not sure what is correct and what cpython does
<mattip>
it seems there are two levels of handle management in PyPy:
<mattip>
the c layer that stores information in the context.info, and the rpython HandleManager
otisolsen70 has quit [Quit: Leaving]
<mattip>
currently, hpy.universal._debug is the C context, so all the _debug interfaces like get_closed_handles don't go through the DebugHandleManager
lritter has joined #pypy
lritter has quit [Ping timeout: 268 seconds]
Atque has quit [Quit: ...]
Atque has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Atque has quit [Client Quit]
jcea has joined #pypy
derpydoo has quit [Ping timeout: 268 seconds]
jcea has quit [Quit: jcea]
jcea has joined #pypy
<Hodgestar>
mattip: I would expect the debug mode to keep handles alive a bit longer now that it keeps track of handles that have been closed. I know very little about the PyPy implementation of debug mode though and you seem to have discovered some complexities I wasn't aware of.
<Hodgestar>
mattip: The debug mode sort of has to keep some information on the C level since it's for debugging C (and thus it is nice to have that information in printing and gdb).