infernix has joined #pypy
graingert[m] has quit [Ping timeout: 256 seconds]
jevinskie[m] has quit [Ping timeout: 260 seconds]
alice has quit [Ping timeout: 260 seconds]
leshaste has joined #pypy
lessshaste has quit [Read error: Connection reset by peer]
alice has joined #pypy
graingert[m] has joined #pypy
stkrdknmibalz has quit [Ping timeout: 256 seconds]
Atque has quit [Ping timeout: 240 seconds]
alice has quit [Ping timeout: 240 seconds]
alice has joined #pypy
Atque has joined #pypy
jevinskie[m] has joined #pypy
jacob22 has quit [Ping timeout: 252 seconds]
lesshaste has joined #pypy
leshaste has quit [Read error: Connection reset by peer]
jacob22 has joined #pypy
Atque has quit [Quit: ...]
lritter has joined #pypy
<
fijal>
I think our ctypes is overengineered
<
fijal>
I presume I'm the one who overengineered it
Guest96 has joined #pypy
otisolsen70 has joined #pypy
Guest96 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Guest96 has joined #pypy
jacob22 has quit [Ping timeout: 276 seconds]
<
cfbolz>
Now I wonder what nulano is up with the parser
<
cfbolz>
antocuni: thinking more about hpy and how graalpython does handles, I now wonder whether we could even tag integers in cpyext
<
antocuni>
cfbolz: uhm... I cannot think of any obvious reason for why it shouldn't work
<
antocuni>
but there might be tons of non-obvious reasons of course :)
<
antocuni>
like, what about code which does pyobj->ob_type?
<
cfbolz>
antocuni: isn't that all nicely in functions or macros now?
<
cfbolz>
yes, it would likely break binary compatibility for cpyext the first time ;-)
<
antocuni>
it's likely that there are still people around using it, but yes it's solvable
<
cfbolz>
antocuni: I am not really sure it would help a huge amount, but it might be worth a try
<
fijal>
of course pypy-c only starts by accident, because it fails to import the cffi ssl module
<
fijal>
if it does not fail to do that, it crashes
Guest96 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Guest96 has joined #pypy
<
fijal>
yay, I have working pypy-c py.test on at least callbacks (variadic functions next)
<
fijal>
ok, getting somewhere, seems I can get pypy-c running well enough, with no jit
<
cfbolz>
fijal: that sounds pretty good, honestly?
<
fijal>
cfbolz: I think the really good news is that libffi has the right fixes
stkrdknmibalz has joined #pypy
slav0nic has joined #pypy
reneeontheweb has joined #pypy
lritter has quit [Quit: Leaving]
Guest96 has joined #pypy
Guest96 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
otisolsen70_ has joined #pypy
otisolsen70 has quit [Ping timeout: 240 seconds]
otisolsen70_ has quit [Remote host closed the connection]
slav0nic has quit [Ping timeout: 252 seconds]
reneeontheweb has quit [Quit: Client closed]
[Arfrever] has quit [Read error: Connection reset by peer]
[Arfrever] has joined #pypy