00:27
fotis has joined #pypy
01:01
fotis has quit [Ping timeout: 252 seconds]
01:31
fotis has joined #pypy
02:07
fotis has quit [Ping timeout: 258 seconds]
02:43
fotis has joined #pypy
03:17
fotis has quit [Ping timeout: 252 seconds]
03:49
fotis has joined #pypy
04:23
fotis has quit [Ping timeout: 265 seconds]
04:30
fotis has joined #pypy
04:34
fotis has quit [Ping timeout: 252 seconds]
05:03
fotis has joined #pypy
05:38
fotis has quit [Ping timeout: 258 seconds]
05:40
fotis has joined #pypy
05:44
fotis has quit [Ping timeout: 252 seconds]
06:11
fotis has joined #pypy
06:46
fotis has quit [Ping timeout: 265 seconds]
07:20
fotis has joined #pypy
07:54
fotis has quit [Ping timeout: 252 seconds]
07:56
fotis has joined #pypy
08:00
fotis has quit [Ping timeout: 265 seconds]
08:27
fotis has joined #pypy
09:01
fotis has quit [Ping timeout: 258 seconds]
09:31
fotis has joined #pypy
10:05
fotis has quit [Ping timeout: 265 seconds]
10:40
fotis has joined #pypy
11:14
fotis has quit [Ping timeout: 252 seconds]
11:16
fotis has joined #pypy
11:20
fotis has quit [Ping timeout: 265 seconds]
11:54
fotis has joined #pypy
12:32
fotis has quit [Ping timeout: 265 seconds]
13:05
fotis has joined #pypy
13:43
fotis has quit [Ping timeout: 252 seconds]
14:17
fotis has joined #pypy
14:26
Julian has joined #pypy
14:33
ronan__ is now known as ronan
14:34
lritter has joined #pypy
14:51
fotis has quit [Ping timeout: 258 seconds]
14:51
fotis has joined #pypy
14:53
stkrdknmibalz has quit [Quit: WeeChat 3.0.1]
14:56
fotis has quit [Ping timeout: 252 seconds]
15:25
fotis has joined #pypy
15:44
Julian has quit [Ping timeout: 265 seconds]
15:59
fotis has quit [Ping timeout: 265 seconds]
16:30
fotis has joined #pypy
16:36
<
mattip >
looking into the test_sys failure on py3.8, it is because we do not bother destroying instances at interpreter shut-down
16:37
<
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
16:38
stkrdknmibalz has joined #pypy
17:07
fotis has quit [Ping timeout: 258 seconds]
17:37
fotis has joined #pypy
18:11
fotis has quit [Ping timeout: 265 seconds]
18:42
<
arigato >
mattip: we never wipe out any module at shotdown, as far as I know
18:42
<
arigato >
what is the captured 'err'?
18:43
fotis has joined #pypy
18:43
<
arigato >
it's obvious, there is no 'gc.collect()' so that destructor is never run in pypy
18:44
<
arigato >
you need to add 'del a; import gc; gc.collect()' in the script
18:45
<
arigato >
or actually, if you do that then the meaning of the test might change in cpython
18:45
<
arigato >
so better to completely skip this test on non-cpython platforms because it doesn't make really sense there
19:00
<
cfbolz >
it's a documented difference that we don't call all destructors at shutdown
19:00
<
cfbolz >
(we only flush files and call atexit functions)
19:00
<
mattip >
right, on a practical level the test should be skipped
19:01
<
mattip >
I am wondering why they make such a big deal about carefully calling all the object destructors
19:02
<
arigato >
also, why they still manually hack their modules so that all destructors are supposed to be very careful
19:20
fotis has quit [Ping timeout: 265 seconds]
19:22
Julian has joined #pypy
19:47
fotis has joined #pypy
19:55
lritter has quit [Quit: Leaving]
20:22
fotis has quit [Ping timeout: 258 seconds]
20:48
fotis has joined #pypy
21:22
fotis has quit [Ping timeout: 265 seconds]
21:24
fotis has joined #pypy
21:29
fotis has quit [Ping timeout: 265 seconds]
22:00
fotis has joined #pypy
22:34
fotis has quit [Ping timeout: 258 seconds]
23:02
fotis has joined #pypy
23:03
az_ has joined #pypy
23:38
fotis has quit [Ping timeout: 265 seconds]