cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
<cfbolz>
mattip: I don't know, I am just seeing it in the profile
<cfbolz>
heh, bit sad: pypy takes 12s on the C++ code, cpy 5s. the total runtime is the same (~30s), meaning that the JIT helps a lot, but the gains are offset by the cpyext slowdowns
<cfbolz>
in other news, I should really actually finish some of my branches ;-)
<mattip>
also other news: if HPy finds someone to do a logo/icon, PyPy could use a new ico file in pypy/goal
<mattip>
the one I made from the logo is not that good
<cfbolz>
that stuff's hard indeed :-(
<nulano>
mattip, I'm not sure it's worth fixing cpyext on PyPy2 for win64
<nulano>
there are a lot more issues than on py3
<mattip>
nulano: I doubt anyone is actually using it in practice, but not having it messes up CI runs
<mattip>
let's see if the branch translates
<antocuni>
cfbolz: what you find matches my experience. Our C performance is so awful that eats everything that we win in pure-python. This was of the reasons why I wanted to start hpy :)
<nulano>
mattip, at the very least I wouldn't release it without carefully checking the API. For example, py2 has 32-bit hashes even on win64 (unlike py3)
<mattip>
ahh
<cfbolz>
antocuni: I am less pessimistic in practice
<mattip>
ok, I will ask the cibuildwheel people if they can deal with missing cpyext on win64-python2.7
<antocuni>
cfbolz: what do you mean?
<mattip>
nulano ^^^
<cfbolz>
antocuni: there's a lot of pure python code around
<cfbolz>
but yes, we need to break even on C code
<cfbolz>
in the long run
<antocuni>
yes, that's my point
<cfbolz>
but still, we need to fix the papercuts too
nimaje has quit [Quit: WeeChat 3.0.1]
<antocuni>
sure, we need to to both
nimaje has joined #pypy
<nulano>
mattip, I wonder whether effectively removing cpyext from py2 on win might surprise someone given the faq states that pypy2 "will be around 'forever'"
<nulano>
but that can be justified by the fact that rpython doesn't need cpyext