fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 268 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 245 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 245 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 245 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 245 seconds]
fotis has joined #pypy
<
mattip>
every translation leaves a 1GB usession directory. Our policy is to leave 3 old usession directories around
<
mattip>
so if we build py3.7, py3.8, default, release-2.7, release3.7, release3.8 that is 6*3 or 18GB of tmp cruft
<
mattip>
on the windows and arm64 buildbot we have about 10GB of tmp space, so they keep filling up
<
fijal>
mattip: maybe we should have removal of usession as an option that is run on buildbot? seems sane to me
<
fijal>
also, all you
*actually* need to do is to make clean, which removes most of it, but nothing of value
<
fijal>
maybe it's a sensible thing to do always
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
<
cfbolz>
fijal: yes, agreed
<
cfbolz>
I think "make clean" is safe to always run
Atque has joined #pypy
fotis has joined #pypy
Atque has quit [Ping timeout: 276 seconds]
fotis has quit [Ping timeout: 245 seconds]
AxTheB has joined #pypy
AxTheB has quit [Remote host closed the connection]
fotis has joined #pypy
otisolsen70 has joined #pypy
wleslie_ has joined #pypy
wleslie_ has quit [Quit: ~~~ Crash in JIT!]
wleslie has joined #pypy
wleslie has quit [Client Quit]
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 268 seconds]
otisolsen70_ has joined #pypy
otisolsen70 has quit [Ping timeout: 265 seconds]
otisolsen70 has joined #pypy
otisolsen70_ has quit [Ping timeout: 268 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
otisolsen70 has quit [Quit: Leaving]
fotis has quit [Ping timeout: 265 seconds]
slav0nic has joined #pypy
fotis has joined #pypy
Atque has joined #pypy
slav0nic has quit [Remote host closed the connection]
fotis has quit [Ping timeout: 245 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 260 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
Atque has quit [Quit: ...]
fotis has quit [Ping timeout: 260 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
danchr_ has joined #pypy
danchr_ has quit [Client Quit]
danchr_ has joined #pypy
danchr_ is now known as danchr
<
mattip>
for packages like vmprof, would it make sense to put a pure-python wheel on PyPI with the tag pp3-none-any ?
<
mattip>
but moved to "ok, if someone can submit a PR we can consider it"
<
mattip>
the the question is where to rank it in the preferences (it is only for pypy, cpython uses py3-none-any)
<
mattip>
I think it should be first, we would always prefer a pure-python wheel over a cpyext one, correct?
fotis has quit [Ping timeout: 265 seconds]
jryans has quit [Quit: Bridge terminating on SIGTERM]
graingert[m] has quit [Quit: Bridge terminating on SIGTERM]
ambv has quit [Quit: Bridge terminating on SIGTERM]
the_drow has quit [Quit: Bridge terminating on SIGTERM]
jryans has joined #pypy
ambv has joined #pypy
graingert[m] has joined #pypy
the_drow has joined #pypy
fotis has joined #pypy
Julian has joined #pypy
<
mattip>
arigato: could you document the workflow to update cffi files in a README somewhere?
<
mattip>
we are out of sync with upstream which has 1.15
fotis has quit [Ping timeout: 260 seconds]
<
ronan>
mattip: we should usually prefer a pure-python wheel, but maybe not always
fotis has joined #pypy
<
mattip>
my thinking is that if someone went to the effort to provide a pure-python pypy-specific wheel, we should prefer it over any cpyext wheels
<
ronan>
mattip: but why would they provide a cpyext wheel in that case?
<
ronan>
whereas if the cpyext version is better, they might want to have the pure-python one as a fallback
<
mattip>
yeah, good question
<
ronan>
hmm, though the fallback would probably be a py3-none-any, rather than pypy-specific...
<
mattip>
makes sense, thanks. So py3-none-any should come after all the cpyext wheels, and before py3-none-any
<
mattip>
grr. So pp3-none-any should come after all the cpyext wheels, and before py3-none-any
<
ronan>
yes, I guess
<
ronan>
though I don't know if people actually do that
jacob22 has joined #pypy
fotis has quit [Ping timeout: 240 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
<
mattip>
heh, it turns out the setup-python github action has dropped the pypy3 specifier
<
mattip>
I wonder how many projects are getting broken CI
fotis has quit [Ping timeout: 252 seconds]
<
Julian>
I stopped using `pypy3` as soon as the other one came out
<
Julian>
so thankfully not mine
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 265 seconds]
Julian has quit [Quit: leaving]
asdgdgasdg has joined #pypy
fotis has joined #pypy
fotis has quit [Ping timeout: 245 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 245 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 252 seconds]
fotis has joined #pypy
fotis has quit [Ping timeout: 245 seconds]