06:10 <fijal> sam_: there are some serious issues in places where the C extension is optional, but untested

06:10 <fijal> the original python code tends to have more bugs, for example

06:10 <fijal> or slight differences in say, atomicity

06:13 <mattip> fijal: what are you suggesting gentoo do?

06:14 <mattip> if projects ship optional python code, I imagine they are willing to accept bug reports when that code does not work

06:16 <fijal> I don't know if I have good answers what should gentoo do

06:16 <fijal> in general it gets filed as "pypy does not work", just like places where people fail to provide source packages

06:16 <fijal> (and pip does some whack shit to obscure the error)

06:21 <mattip> I prefer "pypy does not work, please support it in this library" over "pypy is slow, why use it",

06:21 <mattip> especially if the library has gone to the effort to supply a pypy-alternative pure python implementation

06:22 <sam_> fijal: it's a fair point, but we do run test suites very aggressively at least, and I feel like right now it's going to give people the wrong impression if we allow building extensions by default for pypy, given it's just going to be slow as hell

06:23 <fijal> as I said, no good answers from me

15:12 <lesshaste> should I expect scipy to work with pypy these days?

15:13 <lesshaste> it seems to install but I can't tell if some of the functions won't work

15:15 <lesshaste> hmm.. the answer appears to be yes!

15:55 <mattip> lesshaste: are you using the binary from conda? It passes tests there

15:55 <lesshaste> mattip, sadly pip only

15:55 <lesshaste> but it seemed to install and run!

15:55 <lesshaste> not only that, dlib seemed to install and run too!!

15:56 <lesshaste> mattip, is that unexpected?

15:56 <lesshaste> oh.. did you mean a pypy binary from conda?