<cfbolz>
(sends requests in bunches of 100, sometimes it takes 0.001s, sometimes 3s)
<cfbolz>
seems to correlate with the tls connection dropping
<fijal>
i run more per loop
<fijal>
but you need a localhost web server i think
<cfbolz>
Right
<cfbolz>
Later
<cfbolz>
fijal: anyway, if the connection drops, the numbers are meaningless
<fijal>
yeah
llanhmod has quit [Ping timeout: 268 seconds]
otisolsen70 has joined #pypy
LarstiQ has quit [Remote host closed the connection]
LarstiQ has joined #pypy
<ctismer_>
cfbolz: Hi! Was there something changed between PyPy3.7 and 3.8? I have problems building PySide
<ctismer_>
cfbolz: (BTW.: although there are errors, there are so many examples running that we announce it, now :) )
<ctismer_>
cfbolz: no, was just a setuptools glitch. Distutils was more `idempotent`.
<cfbolz>
ctismer_: cool!
<cfbolz>
Where are you announcing it btw?
<cfbolz>
Do you think it's far enough that we should write a blog post about it?
<ctismer_>
cfbolz: ATM only in our documentation pages, as new feature for PySide 6.3 (comes in a few weeks). I will tell the story and show what works and what not, how to install and so on. I also still have trouble installing scipy stuff.
<cfbolz>
ctismer_: excellent, let's wait for the release then
<ctismer_>
cfbolz: Yes, I think it is far enough. Did not realize that when desperately searching why certain signals do not work, but we got only 9 of 134 examples not working.
<ctismer_>
cfbolz: One funny finding was `QPainter`. That object is often created without closing it, creating many errors in PyPy. Until I recognized that this should be a contest manager since many years 😂
<cfbolz>
ctismer_: that sounds like progress
<ctismer_>
cfbolz: context manager, that automatically calls painter.end()
<ctismer_>
Yes. I'm waiting for the next version, so I can get certain extensions without building.
<ctismer_>
(because scipy and sci-image drive me crazy and conda collides too (trying since days))
<cfbolz>
That's beyond my pay grade 😂
lritter has joined #pypy
<mattip>
the problem with getting pypy into scipy CI is that tests run very slow
<mattip>
most of the code uses cython/pythran/pybind11
<mattip>
and it is hard to convince them to release a wheel if they don't run the tests
<mattip>
(justifyably)
<ctismer_>
mattip: And with wheels it would work fine, but I need the nightly build until my changes are officially in.
<ctismer_>
BTW., is it planned to have PyPy 3.9 in the release, or will it be 3.8, still?
<cfbolz>
ctismer_: 3.8, plus 3.9 alpha
<ctismer_>
cfbolz: ok, so I should stick with 3.8 for now.
<cfbolz>
ctismer_: yep
Atque has quit [Ping timeout: 276 seconds]
Atque has joined #pypy
Guest96 has joined #pypy
greedom has joined #pypy
greedom has quit [Remote host closed the connection]
greedom has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Ninpo_ is now known as Ninpo
Ninpo has quit [Changing host]
Ninpo has joined #pypy
alicetries has quit [Remote host closed the connection]
alice has joined #pypy
alice is now known as Guest4619
Guest4619 has quit [Quit: *disappears* U_U]
alice has joined #pypy
alice is now known as Guest865
Guest865 has quit [Killed (osmium.libera.chat (Nickname regained by services))]
alice has joined #pypy
alice is now known as adequatealice
adequatealice has left #pypy [#pypy]
greedom has quit [Remote host closed the connection]
otisolsen70_ has joined #pypy
otisolsen70_ has quit [Remote host closed the connection]
otisolsen70 has quit [Ping timeout: 240 seconds]
lritter has quit [Quit: Leaving]
Guest96 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]