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 | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
infernix has quit [Server closed connection]
infernix has joined #pypy
pvital has quit [Server closed connection]
pvital has joined #pypy
sthalik has quit [Server closed connection]
dmalcolm_ has joined #pypy
dmalcolm has quit [Ping timeout: 255 seconds]
archie2342345234 has joined #pypy
<archie2342345234> I'm trying to use a c/c++ library with cffi. The library is multithreaded under the hood, and it glitches in random ways (is slow and quits abruptly every other time, but no segfaults etc). But it seems to work without any issues if I do all cffi calls in any thread other than the main one. I guess this probably has something to do with the GIL? Maybe is this an issue that is known to pop up with threaded C libraries in general and
<archie2342345234> someone could give up some general directions in fixing such stuff? The same behavior is observed both on PyPy3 and CPython
ruth07309354 has joined #pypy
[Arfrever] has quit [Ping timeout: 255 seconds]
[Arfrever] has joined #pypy
sugarbeet has quit [Server closed connection]
sugarbeet has joined #pypy