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 quit [Ping timeout: 244 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 272 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 272 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 244 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 272 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 264 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 272 seconds]
otisolsen70 has joined #pypy
fotis has joined #pypy
Julian has joined #pypy
Julian has quit [Client Quit]
fotis has quit [Ping timeout: 244 seconds]
antocuni_ is now known as antocuni
Dejan has joined #pypy
fotis has joined #pypy
fotis has quit [Ping timeout: 272 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 244 seconds]
fotis has joined #pypy
Dejan has quit [Quit: Leaving]
Dejan has joined #pypy
lehmrob has joined #pypy
fotis has quit [Ping timeout: 244 seconds]
fotis has joined #pypy
<arigato> can we even run any RPython code while PyErr_Occurred() returns non-null? or are we supposed to handle it all in C?
<arigato> ah no, forget what I just said. there is ExecutionContext.cpyext_operror
fotis has quit [Ping timeout: 264 seconds]
fotis has joined #pypy
Julian has joined #pypy
fotis has quit [Ping timeout: 272 seconds]
<mattip> it seems a segfault is not the best response though
Julian has quit [Quit: leaving]
Julian has joined #pypy
<cfbolz> mattip: I finally fixed max
fotis has joined #pypy
<cfbolz> the first two commits by the MS speed team landed in cpython main, btw
<cfbolz> they look reasonable
<cfbolz> it's a bit of an improvement of our LOAD_METHOD interpreter speedups
<cfbolz> And we don't even have a LOAD_GLOBAL cache any more
fotis has quit [Ping timeout: 264 seconds]
<mattip> cool to both the items
fotis has joined #pypy
<cfbolz> Would be a good masters thesis
<fijal> pfff, [1, 2, 3, 4] == range(4)
<fijal> False
<Dejan> [0, 1, 2, 3] == list(range(4))
fotis has quit [Ping timeout: 272 seconds]
<fijal> Dejan: yeah I know, it's a bit frustrating, maybe it should either compare or say "uh this makes no sense"
fotis has joined #pypy
<mgorny> fijal: it compares against the generator
<mgorny> In [1]: range(4) == range(4)
<mgorny> Out[1]: True
<fijal> >>>> iter([1, 2, 3, 4]) == range(4)
<fijal> False
<fijal> that should be true then?
<mgorny> no, iterator != range
<mgorny> also it's [0,1,2,3]
Julian has quit [Ping timeout: 272 seconds]
<fijal> so what's "comparison against a generator" then?
Julian has joined #pypy
Julian has quit [Ping timeout: 268 seconds]
fotis has quit [Ping timeout: 240 seconds]
Julian has joined #pypy
<Dejan> the original example is comparison against a generator
stkrdknmibalz has quit [Quit: WeeChat 3.0.1]
fotis has joined #pypy
lehmrob has quit [Read error: Connection reset by peer]
<ronan> range(4) is a sequence, not a generator or an iterator
<ronan> the original example is consistent with (0, 1, 2, 3) != [0, 1, 2, 3]
<ronan> sequences of different types compare different even if they have the same elements
Julian has quit [Ping timeout: 265 seconds]
fotis has quit [Ping timeout: 268 seconds]
Julian has joined #pypy
Julian has quit [Ping timeout: 268 seconds]
Julian has joined #pypy
fotis has joined #pypy
Julian has quit [Ping timeout: 268 seconds]
Julian has joined #pypy
<LarstiQ> which sequence other than range(4) would compare equal to that? (0, 1, 2, 3) does not
Julian has quit [Ping timeout: 240 seconds]
fotis has quit [Ping timeout: 240 seconds]
fotis has joined #pypy
Julian has joined #pypy
fotis has quit [Ping timeout: 272 seconds]
Julian has quit [Quit: leaving]
<Corbin> What are the RPython options for low-level storage of a matrix of bits, e.g. to store a dense directed graph?
* Corbin knows the answer but was feeling optimistic
Dejan has quit [Quit: Leaving]
stkrdknmibalz has joined #pypy
fotis has joined #pypy
<cfbolz> Corbin: nothing built in
<cfbolz> Bytearray and do the work
fotis has quit [Ping timeout: 240 seconds]
<Corbin> Yep, completely fair answer.
fotis has joined #pypy
fotis has quit [Ping timeout: 268 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 240 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 268 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 240 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 244 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 240 seconds]
fotis has joined #pypy
otisolsen70 has quit [Quit: Leaving]
<mattip> the scipy classes around this weird segfault have huge docstrings. Do we care?
fotis has quit [Ping timeout: 272 seconds]
<mattip> it seems to be repeatable across runs, but random if I shift things in the code
<mattip> which might mean a stack overflow?
fotis has joined #pypy
fotis has quit [Read error: Connection reset by peer]
fotis has joined #pypy
fotis has quit [Ping timeout: 240 seconds]
fotis has joined #pypy