antocuni changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | "PyPy: the Gradual Reduction of Magic (tm)"
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 248 seconds]
antocuni has joined #pypy
yuyichao has quit [Ping timeout: 265 seconds]
pilne has joined #pypy
dcrosta has joined #pypy
marky1991 has quit [Read error: Connection reset by peer]
yuyichao has joined #pypy
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
tbodt has joined #pypy
__main__ has quit [Read error: Connection reset by peer]
__main__ has joined #pypy
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 272 seconds]
marr has quit [Ping timeout: 255 seconds]
dcrosta has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
ronan has quit [Ping timeout: 255 seconds]
adamholmberg has joined #pypy
antocuni has quit [Ping timeout: 248 seconds]
ronan has joined #pypy
tbodt has joined #pypy
fryguybob has quit [Ping timeout: 265 seconds]
rguillebert_ has joined #pypy
mat^2 has quit [Ping timeout: 240 seconds]
wallet42_ has joined #pypy
Hexxeh____ has joined #pypy
dustinm- has joined #pypy
fryguybob has joined #pypy
__main__ has quit [*.net *.split]
dustinm has quit [*.net *.split]
mvantellingen has quit [*.net *.split]
rguillebert has quit [*.net *.split]
static- has quit [*.net *.split]
wallet42 has quit [*.net *.split]
Hexxeh___ has quit [*.net *.split]
rguillebert_ is now known as rguillebert
wallet42_ is now known as wallet42
static has joined #pypy
__main__ has joined #pypy
danieljabailey has quit [Ping timeout: 240 seconds]
chris| has quit [Ping timeout: 240 seconds]
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
ulope has quit [Ping timeout: 260 seconds]
chris| has joined #pypy
danieljabailey has joined #pypy
ulope has joined #pypy
mvantellingen has joined #pypy
<njs> this is a long shot, but anyone have any guesses why this test would occasionally freeze on PyPy? https://github.com/python-trio/trio/blob/master/trio/_core/tests/test_local.py#L97-L130
<simpson> Is there a JSON parser available for RPython?
<njs> it's happened ~3 times now over the last 6 months, only on PyPy, so kind of mysterious
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
<pjenvey> njs: q.get() blocking because the first put wasn't called yet?
<njs> pjenvey: which q.get()? the one at the top of main()? the test runs two copies of main() in child threads, then the parent thread does put/get calls to force the children to execute in a particular order
<pjenvey> er no im stupid
<njs> it is a little confusing
<pjenvey> can I ignore the _core.RunLocal, im not sure what this does
<njs> pjenvey: RunLocal is basically an implementation of thread-locals, the test is checking that the two threads don't see each other's values (i.e., it's actually thread-local)
<njs> I'm much more suspicious of the threads and the queues causing problems than RunLocal, though who knows, maybe RunLocal has some kind of evil buried inside it :-)
adamholmberg has quit [Ping timeout: 264 seconds]
jcea has quit [Quit: jcea]
<pjenvey> njs: nothing obvious, if you can catch it when it happens pypy3 actually supports faulthandler.dump_traceback
<njs> pjenvey: I haven't managed to repro it locally yet, but good to know. does it also support faulthandler.dump_traceback_later?
ArneBab_ has joined #pypy
<njs> pjenvey: that could be a useful thing to have enabled in general on CI runs...
<pjenvey> njs: i suppose there could be potentially be enough lag in the thread start
ArneBab has quit [Ping timeout: 256 seconds]
<njs> pjenvey: not sure what you mean?
<pjenvey> njs: add a few second sleep to the beginning of main...
pilne has quit [Quit: Quitting!]
yuyichao has quit [Quit: Konversation terminated!]
dddddd has quit [Quit: Hasta otra..]
marky1991 has joined #pypy
marky1991 has quit [Ping timeout: 260 seconds]
<njs> ugh, getting faulthandler and pytest to play nicely together seems to be non-trivial
<njs> pjenvey: if I add a few second sleep to the beginning of main(), doesn't that just mean that the main thread blocks for a bit in q1.get()?
<njs> pjenvey: still passes for me
riddle has quit [Disconnected by services]
lukasa has quit [Ping timeout: 255 seconds]
infernix has quit [Ping timeout: 255 seconds]
riddle has joined #pypy
lukasa has joined #pypy
chris| has quit [Ping timeout: 240 seconds]
danieljabailey has quit [Ping timeout: 260 seconds]
<kenaan> mattip py3.5 0fda157e0d0e /pypy/interpreter/pycode.py: fix translation?
danieljabailey has joined #pypy
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3586 [mattip: force build, py3.5]
chris| has joined #pypy
<kenaan> mattip default 0b47a415bba3 /rpython/rlib/rvmprof/cintf.py: exclude win32
dowwie has quit [Ping timeout: 248 seconds]
dowwie has joined #pypy
dowwie has joined #pypy
dowwie has quit [Changing host]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/768 [mattip: force build, py3.5]
dcrosta has joined #pypy
infernix has joined #pypy
jamesaxl has joined #pypy
oberstet has joined #pypy
ctismer_afk has joined #pypy
jamesaxl has quit [*.net *.split]
ssbr` has quit [*.net *.split]
ctismer has quit [*.net *.split]
webmeister has quit [*.net *.split]
samth has quit [*.net *.split]
sbauman has quit [*.net *.split]
tito has quit [*.net *.split]
jeroud has quit [*.net *.split]
MarkMangoba has quit [*.net *.split]
asmeurer has joined #pypy
redj has quit [Remote host closed the connection]
jamesaxl has joined #pypy
redj has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/768 [mattip: force build, py3.5]
danieljabailey has quit [Ping timeout: 240 seconds]
danieljabailey has joined #pypy
sbauman has joined #pypy
tito has joined #pypy
jeroud has joined #pypy
MarkMangoba has joined #pypy
webmeister has joined #pypy
samth has joined #pypy
ssbr` has joined #pypy
ssbr` has quit [*.net *.split]
webmeister has quit [*.net *.split]
samth has quit [*.net *.split]
sbauman has quit [*.net *.split]
tito has quit [*.net *.split]
jeroud has quit [*.net *.split]
MarkMangoba has quit [*.net *.split]
tito has joined #pypy
tito has quit [Changing host]
tito has joined #pypy
samth has joined #pypy
ssbr` has joined #pypy
sbauman has joined #pypy
jeroud has joined #pypy
<njs> LarstiQ: that is what I ended up with :-) https://github.com/python-trio/trio/pull/384
MarkMangoba has joined #pypy
webmeister has joined #pypy
<LarstiQ> other than that my response would be "maybe arigato is interested in fun threading problems"
dowwie has quit [Ping timeout: 248 seconds]
dowwie has joined #pypy
jamesaxl has quit [Read error: Connection reset by peer]
jamesaxl has joined #pypy
oberstet has quit [Ping timeout: 252 seconds]
realitix has joined #pypy
jneen has quit [Remote host closed the connection]
oberstet has joined #pypy
ctismer_afk is now known as ctismer
<kenaan> fijal release-pypy3.5-v5.9.x 067f612e97ae /: merge py3.5
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/5629 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/6465 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1640 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-s390x/builds/803 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5177 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/769 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raspbian/builds/1774 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armel/builds/2018 [dev: force build, release-pypy3.5-v5.9.x]
<arigato> fijal: so, on Windows pypy3 kind of works, except many details
<arigato> pillow and numpy both get compilation errors
<arigato> unclear why but I didn't look in detail
marr has joined #pypy
<fijal> yeah
<fijal> arigato: I think it's ok to call it "beta"
<fijal> and then maybe we improve
<fijal> I'll add what we want to go to 6.0 I think
<fijal> (to the release announcement)
<fijal> arigato: I just tested btw, it's sort of "good enough" or something
<arigato> yes, maybe sense
<arigato> yeah, people actually have been using pypy3 already, strangely
<fijal> maybe not on windows
<arigato> likely not
<fijal> numpy error looks like it's a numpy problem not pypy
<fijal> (remember that numpy officially discourages installing via pip)
<fijal> or more likely, ancient VS that pypy is using is not compatible with the way it's written
<fijal> we should really update the VS version
antocuni has joined #pypy
dowwie has quit [Ping timeout: 264 seconds]
dowwie has joined #pypy
Jellyg00se has joined #pypy
Remi_M has quit [Ping timeout: 246 seconds]
Remi_M has joined #pypy
<kenaan> antocuni default 726f599fb32a /extra_tests/test_vmprof_greenlet.py: skip this test on platforms where _vmprof is not built
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/769 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5177 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/6465 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Success: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armel/builds/2018 [dev: force build, release-pypy3.5-v5.9.x]
<kenaan> rlamy py3.5 a3e4d351acbe /lib-python/3/ssl.py: Backout lib-python/ change in 4bb7cf3
<LarstiQ> ronan: what is that backout for?
* LarstiQ couldn't tell from looking at hg log
<ronan> that looked like leftover debugging code
<LarstiQ> aah, yeah, could be
<ronan> it caused a bunch of DirEntry related failures
<LarstiQ> check
<ronan> arigato: did I guess right?
<arigato> yes, indeed
<arigato> thanks
<bbot2> Success: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raspbian/builds/1774 [dev: force build, release-pypy3.5-v5.9.x]
<arigato> fijal: ^^ needs to be merged to release-pypy3.5, sorry about that
<fijal> arigato: cool, should we restart the buildbots?
antocuni has quit [Ping timeout: 248 seconds]
<ronan> fijal: I have another fix
dddddd has joined #pypy
Remi_M has quit [Ping timeout: 272 seconds]
squeaky_pl has joined #pypy
<squeaky_pl> For the upcoming release I am kind of confused. I see 5.10 and 5.11 versions mentioned in the commit messages but you keep merging stuff into release-pypy3.5-v5.9.x.
Remi_M has joined #pypy
<squeaky_pl> What would be the next version for pypy and pypy3 and what would be the corresponding hg branches?
* squeaky_pl warming up his engines
mattip_away has joined #pypy
<LarstiQ> squeaky_pl: afaiui, a small 5.10 release for both pypy2/3 now, and 6.0 early next year. Release branches are still getting made
<LarstiQ> iirc mattip mentioned making a pypy2 branch, would need to check irclog
<mattip_away> fijal: did you want the vmprof fixes from default in the 3.5 release?
<fijal> squeaky_pl: yes, that's confusion caused by someone wanting 5.9.1
<fijal> mattip_away: likely
<mattip_away> it seems the cuurnet default looks clean enough to branch a release off of it
<mattip_away> i can get it going later today
<mattip_away> some -A test on win32 py3.5 is still hanging on the buildbot
<squeaky_pl> OK, I will just keep watching. In the meantime I update all the dependencies and get gcc 7.2 to work on Centos 5.
<mattip_away> i kill the pypy3.5.exe process by hand and test run to completion
<mattip_away> but that only works cuz i can access the buildslave
mattip_away has quit [Remote host closed the connection]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-s390x/builds/803 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3588 [dev: force build, release-pypy3.5-v5.9.x]
oberstet has quit [Ping timeout: 252 seconds]
mat^2 has joined #pypy
mat^2 has quit [Client Quit]
oberstet has joined #pypy
tayfun26 has joined #pypy
<ronan> fijal: done, you can merge now
<kenaan> rlamy py3.5 6276a7287d4b /pypy/module/errno/test/test_errno.py: Clean up tests
marr has quit [Ping timeout: 240 seconds]
oberstet has quit [Ping timeout: 252 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 248 seconds]
antocuni has joined #pypy
dowwie has quit [Ping timeout: 252 seconds]
<fijal> ronan: should we merge default -> py3k first?
<fijal> to get vmprof fixes in
dowwie has joined #pypy
<fijal> does not hurt
<kenaan> fijal py3.5 4f88f2f2d3f2 /: merge default
<kenaan> fijal release-pypy3.5-v5.9.x 42207cd2265c /: merge py3.5
<fijal> uh what is that?
exarkun has quit [Read error: Connection reset by peer]
<fijal> arigato: any opinions on the failures?
<fijal> maybe we don't care about armhf, but it seems like stuff should work mostly and the error is crazy
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/6466 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1641 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-s390x/builds/804 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5178 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/770 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raspbian/builds/1775 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armel/builds/2019 [dev: force build, release-pypy3.5-v5.9.x]
<arigato> yes, a bit no clue
<arigato> there is probably a file "testing.py" lying around
<arigato> I think it's meant to import the "testing" from the cffi repo
<arigato> I guess it picks a random other one
<arigato> actually, no clue how it works on x86
<arigato> there is no "testing" when the tests have been copied inside pypy
<arigato> I also cannot find the line at all, either in "default" or in "p3.5"
<arigato> ah
<arigato> /usr/lib/python2.7/dist-packages/cffi/recompiler.py ??
exarkun has joined #pypy
<arigato> things get very confused and it's importing the cffi installed in cpython, which it shouldn't
<fijal> pfff
<arigato> can we leave the arm py3.5 for later? it looks like its errors are hard to make sense of
* arigato starts a round of looking at the new issues in the x86-64 py3.5
<fijal> yeah
adamholmberg has joined #pypy
<arigato> ah, actually ronan already fixed most of them, thanks
oberstet has joined #pypy
mattip_away has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3588 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3589 [dev: force build, release-pypy3.5-v5.9.x]
mattip_away has quit [Client Quit]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/770 [dev: force build, release-pypy3.5-v5.9.x]
marr has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5178 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/5629 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/5630 [dev: force build, release-pypy3.5-v5.9.x]
AndrewBC has joined #pypy
utek has quit [Ping timeout: 248 seconds]
utek has joined #pypy
bgola has quit [Ping timeout: 248 seconds]
<bbot2> Retry: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1641 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1642 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Retry: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3589 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3590 [dev: force build, release-pypy3.5-v5.9.x]
ctismer has quit [Ping timeout: 248 seconds]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/6466 [dev: force build, release-pypy3.5-v5.9.x]
ctismer has joined #pypy
bgola has joined #pypy
tayfun26 has quit [Quit: tayfun26]
<bbot2> Retry: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1642 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Retry: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3590 [dev: force build, release-pypy3.5-v5.9.x]
<ronan> fijal: cffi and ctypes tests are completely bogus on py3.5
<bbot2> Started: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1643 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3591 [dev: force build, release-pypy3.5-v5.9.x]
adamholm_ has joined #pypy
<bbot2> Success: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armhf-raspbian/builds/1775 [dev: force build, release-pypy3.5-v5.9.x]
adamholmberg has quit [Ping timeout: 268 seconds]
<bbot2> Success: http://buildbot.pypy.org/builders/build-pypy-c-jit-linux-armel/builds/2019 [dev: force build, release-pypy3.5-v5.9.x]
<fijal> ronan: on py35 or py35 on arm?
<ronan> py3k in general
<fijal> :/
<fijal> Can we call a release final if cffi is not working?
<fijal> Also I'm confused
<fijal> Ssl which is cffi based works
<ronan> well, cffi probably mostly works, it's just not tested
<fijal> Ok
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/4393 [dev: force build, release-pypy3.5-v5.9.x]
oberstet has quit [Ping timeout: 268 seconds]
ronan has quit [Quit: Ex-Chat]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/5630 [dev: force build, release-pypy3.5-v5.9.x]
Jellyg00se has quit [Quit: Leaving]
oberstet has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-s390x/builds/804 [dev: force build, release-pypy3.5-v5.9.x]
raynold has quit [Quit: Connection closed for inactivity]
mattip has joined #pypy
realitix has quit [Quit: realitix]
raynold has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1643 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3591 [dev: force build, release-pypy3.5-v5.9.x]
<squeaky_pl> hum, _curses_cffi.pypy3-510-x86_64-linux-gnu.so
<squeaky_pl> does that mean that ABI wise 5.10 == 51.0?
<squeaky_pl> I think those things were designed for 1 digit major 1 digit minor
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3586 [mattip: force build, py3.5]
<mattip> squeaky_pl: is it a problem? it means 5.10, just like 58 meant 5.8
<mattip> does pip or anyone else choke on the 3-digit form?
<mattip> py3.5 is broken on win32 after the errno fixes
<kenaan> mattip py3.5 7dce5a70e8e7 /pypy/module/errno/interp_errno.py: fix for MSVC compatibility
<kenaan> mattip release-pypy3.5-v5.9.x ad8e7f9311f5 /pypy/module/errno/interp_errno.py: merge py3.5 into release
<kenaan> mattip release-pypy2.7-v5.9.x 0e7ea4fe15e8 /pypy/module/: make version final
<kenaan> mattip default 6b024edd9d12 /pypy/module/: increment version
<kenaan> mattip default bc445709766c /pypy/doc/: restart whats-new
<kenaan> mattip default 58004bbab6dc /pypy/doc/whatsnew-head.rst: part two of restart whats-new
<bbot2> Failure: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1640 [dev: force build, release-pypy3.5-v5.9.x]
antocuni has quit [Ping timeout: 256 seconds]
<squeaky_pl> mattip, it doenst choke, it was just a random thought
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/4393 [dev: force build, release-pypy3.5-v5.9.x]
<squeaky_pl> Is PyPy3 5.10 final? not alpha not beta?
<squeaky_pl> ah I just saw a commit, it is intentionally final
adamholm_ has quit [Remote host closed the connection]
adamholmberg has joined #pypy
<mattip> squeaky_pl: ok, thought there was yet another problem
adamholmberg has quit [Ping timeout: 240 seconds]
* mattip trying to figure out what to do about missing hastzinfo in our PyDateTime objects
marr has quit [Ping timeout: 268 seconds]
adamholmberg has joined #pypy
ceridwen has quit [Ping timeout: 265 seconds]
tbodt has joined #pypy
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/3483 [dev: force build, release-pypy3.5-v5.9.x]
<nanonyme> Meh, again with packages using CPython C API?
<cfbolz> well, not too surprising. those are important packages
<cfbolz> the answer would be "yes, it's a known problem, should get better in the next release"
<nanonyme> Oh, is something significant happening on that front?
<mattip> cfbolz: by how much? truth be told, I am right now trying to figure out why pandas HEAD is broken for PyPY
<cfbolz> right, and it's only the release after the next
<mattip> with that, I answered :)
ronan has joined #pypy
<mattip> cpyext-avoid-roundtrip now fails as many lxml tests as default (after a two-line fix for negative indexes)
<mattip> so that is good
<mattip> On the other hand, it does not speed up the test run at all
<LarstiQ> does it get slower?
<cfbolz> mattip: thanks
<mattip> LarstiQ: no, but the point was to be faster at stuff. Perhaps the tests are the wrong stuff
adamholmberg has quit [Remote host closed the connection]
<cfbolz> mattip: yes, tests are still a little bit dubious as benchmarks
adamholmberg has joined #pypy
<cfbolz> But I suspect it really shows that the branch is not super great anyway
<mattip> it is a good start, I think you pointed out the poor getitem performance that is probably more of an issue
ceridwen has joined #pypy
ronan has quit [Read error: Connection reset by peer]
ronan__ has joined #pypy
ronan__ is now known as ronan
adamholmberg has quit [Ping timeout: 252 seconds]
<mattip> ok, the pandas problem is due to triggering cython code that expects datetime structs like cpython, where ours are opaque PyObjects
<mattip> it happens to be the very first commit after pandas0.21, and 0.22 has not been released yet, so we still have a chance to reclaim ourselves
<mattip> s/reclaim/redeem/
adamholmberg has joined #pypy
marr has joined #pypy
ronan has quit [Ping timeout: 240 seconds]
<mattip> gnite
mattip has left #pypy ["bye"]
jcea has joined #pypy
squeaky_pl has quit [Ping timeout: 240 seconds]
squeaky_pl has joined #pypy
<bbot2> Retry: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/3483 [dev: force build, release-pypy3.5-v5.9.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/3484 [dev: force build, release-pypy3.5-v5.9.x]
jamesaxl has quit [Quit: WeeChat 1.9.1]
jtl_ has joined #pypy
oberstet has quit [Ping timeout: 252 seconds]
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
tbodt has joined #pypy
tbodt has quit [Read error: Connection reset by peer]
jtl_ has quit [Quit: jtl_]
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 264 seconds]
tbodt has joined #pypy
_whitelogger has joined #pypy