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 | insert pithy quote here
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 258 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 258 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 258 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
Julian has joined #pypy
ronan__ is now known as ronan
lritter has joined #pypy
fotis has quit [Ping timeout: 258 seconds]
fotis has joined #pypy
stkrdknmibalz has quit [Quit: WeeChat 3.0.1]
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
Julian has quit [Ping timeout: 265 seconds]
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
<mattip> looking into the test_sys failure on py3.8, it is because we do not bother destroying instances at interpreter shut-down
<mattip> is there a real-world use case for doing that clean-up? It seems to me to be asking for trouble: who knows what state each module is in when shutting down
stkrdknmibalz has joined #pypy
fotis has quit [Ping timeout: 258 seconds]
fotis has joined #pypy
<mattip> here is the issue https://bugs.python.org/issue20602
fotis has quit [Ping timeout: 265 seconds]
<arigato> mattip: we never wipe out any module at shotdown, as far as I know
<arigato> what is the captured 'err'?
fotis has joined #pypy
<arigato> ah no
<arigato> it's obvious, there is no 'gc.collect()' so that destructor is never run in pypy
<arigato> you need to add 'del a; import gc; gc.collect()' in the script
<arigato> or actually, if you do that then the meaning of the test might change in cpython
<arigato> so better to completely skip this test on non-cpython platforms because it doesn't make really sense there
<cfbolz> I agree
<cfbolz> it's a documented difference that we don't call all destructors at shutdown
<cfbolz> (we only flush files and call atexit functions)
<mattip> right, on a practical level the test should be skipped
<mattip> I am wondering why they make such a big deal about carefully calling all the object destructors
<arigato> also, why they still manually hack their modules so that all destructors are supposed to be very careful
fotis has quit [Ping timeout: 265 seconds]
Julian has joined #pypy
fotis has joined #pypy
lritter has quit [Quit: Leaving]
fotis has quit [Ping timeout: 258 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 258 seconds]
fotis has joined #pypy
az_ has joined #pypy
fotis has quit [Ping timeout: 265 seconds]