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 | so many corner cases, so little time
Techcable has joined #pypy
njs has joined #pypy
<njs> anyone have any guesses about why calling gc.collect() repeatedly could fail to collect an unreachable object, BUT ONLY if running with coverage enabled?
<njs> oh gods, is this another interaction between tracing and fast locals? I'm doing 'del e; print(locals())' and with coverage enabled, the print shows 'e' as still present
Atque has quit [Quit: ...]
slav0nic has joined #pypy
Atque has joined #pypy
<cfbolz> njs: hey :-)
<cfbolz> in pypy or in cpython?
nimaje has quit [Quit: WeeChat 3.3]
nimaje has joined #pypy
Dejan has joined #pypy
Atque has quit [Quit: ...]
Atque has joined #pypy
Dejan has quit [Quit: Leaving]
<mattip> we should really upgrade our coverage support since the first place many library developers meet PyPy is when running CI, and many of them turn on coverage by default
<mattip> so they get a bad impression about pypy from the very first CI run
<mattip> slow, buggy, ...
<mattip> cfbolz: there are a couple of at_exit tests failing in test_threading
<mattip> maybe connected to both njs's report and the compileall problem?
<mattip> on py3.9, which is probably not what njs is testing, but maybe the test fails similarly on older versions...
<cfbolz> mattip: right
<cfbolz> (I'll probably get to it on Monday only)
<mattip> no problem
greedom has joined #pypy
<njs> cfbolz: on pypy, specifically the latest 3.8 release, but based on CI results I suspect the same thing happens on {3.7, 3.8} {release, nightly}
<cfbolz> njs: ok, link?
jacob22 has quit [Ping timeout: 240 seconds]
<Cheery> I'm implementing constraint handling rules into my makeshift ukanren implementation.
<Cheery> I don't know if I get it because it's difficult.
<Cheery> incredibly simple idea, but complicated to implement. There's operational semantics paper that seem like it helps though. :)
slav0nic has quit [Ping timeout: 260 seconds]
<mattip> there is also a test_subprocess test failing on py3.7 and up
<mattip> about signals
infernix has quit [Ping timeout: 245 seconds]
<njs> after the 'del e' on line 720, if you add a 'print(locals())' then 'e' is still present, iff running on pypy under coverage
<njs> I suspect it has to do somehow with the call to `await force_receive_loop_to_start()` capturing 'e' in a cell, even though that frame is dead and gone before the 'del e'
infernix has joined #pypy
greedom has quit [Read error: Connection reset by peer]
greedom has joined #pypy
<mattip> we never implemented posix_spawn for py3.8
Techcable has quit [Ping timeout: 240 seconds]
<Cheery> all right.. I need to read the paper carefully so that I didn't miss anything, but otherwise I have my first constraint handling rule engine.
<Cheery> code or it didn't happen
<Corbin> CHR! Good times.
<cfbolz> njs: thank you
lritter has joined #pypy
slav0nic has joined #pypy
<Cheery> ok. immediately few bugs and issues I didn't notice.
<Cheery> I'll add the rest of the rules tmr. and see how it works in practice.
<Cheery> Also going to finish reading the paper to see if I missed anything important.
<Cheery> I don't have propagation history for instance, but not sure what that is exactly.
Atque has quit [Quit: ...]
greedom has quit [Remote host closed the connection]
greedom has joined #pypy
Techcable has joined #pypy
slav0nic has quit [Ping timeout: 268 seconds]