arigato 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 | mac OS and Fedora are not Windows
adamholmberg has quit [Remote host closed the connection]
Zaab1t has quit [Quit: bye bye friends]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 246 seconds]
lritter has joined #pypy
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
k1nd0f_ has quit [Ping timeout: 246 seconds]
k1nd0f_ has joined #pypy
k1nd0f_ has quit [Ping timeout: 268 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 250 seconds]
lritter has quit [Ping timeout: 246 seconds]
lritter has joined #pypy
inhahe has quit [Read error: Connection reset by peer]
inhahe has joined #pypy
PileOfDirt has quit [Remote host closed the connection]
_whitelogger has joined #pypy
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 250 seconds]
_whitelogger has joined #pypy
dddddd has quit [Remote host closed the connection]
zmt01 is now known as zmt00
Ai9zO5AP has quit [Ping timeout: 246 seconds]
Ai9zO5AP has joined #pypy
themsay has quit [Ping timeout: 245 seconds]
k1nd0f_ has joined #pypy
k1nd0f_ has quit [Ping timeout: 250 seconds]
k1nd0f_ has joined #pypy
themsay has joined #pypy
k1nd0f_ has quit [Ping timeout: 272 seconds]
antocuni has joined #pypy
antocuni has quit [Ping timeout: 250 seconds]
agronholm has joined #pypy
lritter has quit [Ping timeout: 240 seconds]
themsay has quit [Ping timeout: 246 seconds]
themsay has joined #pypy
k1nd0f_ has joined #pypy
k1nd0f_ has quit [Ping timeout: 272 seconds]
dddddd has joined #pypy
antocuni has joined #pypy
jcea has joined #pypy
Arfrever has quit [Ping timeout: 240 seconds]
k1nd0f_ has joined #pypy
adamholmberg has joined #pypy
k1nd0f_ has quit [Ping timeout: 250 seconds]
Zaab1t has joined #pypy
mattip has quit [Ping timeout: 250 seconds]
k1nd0f_ has joined #pypy
mattip has joined #pypy
k1nd0f_ has quit [Ping timeout: 268 seconds]
adamholmberg has quit [Read error: Connection reset by peer]
adamholm_ has joined #pypy
adamholm_ has quit [Remote host closed the connection]
_whitelogger has joined #pypy
jcea has quit [Read error: Connection reset by peer]
jcea1 has joined #pypy
<mattip> there is a new rpython failure, hg bisect points to 432d816c6d7b
jcea1 is now known as jcea
<arigato> ah, that's a new test added in that branch 'gc-disable'
* arigato fixes the test to correspond
<mattip> +1
<kenaan> arigo default de85e0ef8bdc /rpython/memory/gc/test/test_direct.py: fix the test to match 432d816c6d7b
<mattip> does something special happen to format(123, "\u2007<5") after translation?
<mattip> the test for that is failing in lib-python/3/test/test_format.py on unicode-utf8-py
<mattip> but I thought I fixed it
<mattip> ahh, I fixed format(u"abc", u"\u2007<5"). a little different
Ai9zO5AP has quit [Ping timeout: 268 seconds]
Ai9zO5AP has joined #pypy
antocuni has quit [Ping timeout: 250 seconds]
dddddd has quit [Remote host closed the connection]
dddddd has joined #pypy
Arfrever has joined #pypy
xcm has quit [Ping timeout: 245 seconds]
xcm has joined #pypy
k1nd0f_ has joined #pypy
PileOfDirt has joined #pypy
antocuni has joined #pypy
<kenaan> mattip unicode-utf8 25ff5465e2c1 /pypy/objspace/std/: fill_char can be a utf8 multibyte codepoint
xcm has quit [Remote host closed the connection]
<kenaan> mattip unicode-utf8-py3 c01df448bea6 /pypy/objspace/std/: merge unicode-utf8 into branch
xcm has joined #pypy
k1nd0f_ has quit [Ping timeout: 245 seconds]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5939 [mattip: force build, unicode-utf8-py3]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7213 [mattip: force build, unicode-utf8-py3]
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
xcm has quit [Remote host closed the connection]
antocuni has quit [Ping timeout: 272 seconds]
xcm has joined #pypy
<mjacob> arigato: what's the correct way to use revdb with python 3.x? i see that the revdb repo has a 'py3' branch, but it seems outdated
<mjacob> arigato: s/outdated/unfinished/
WGH has joined #pypy
k1nd0f_ has joined #pypy
k1nd0f_ has quit [Remote host closed the connection]
<arigato> mjacob: I think that it should just work nowadays
<arigato> at least if you mean running "python3 revdb.py"
<arigato> ...ok no
<mjacob> i don't care whether revdb.py is run with python2 or python3 really
<arigato> yes, ok
<arigato> then the problem is that pypy's py3.5 branch doesn't support revdb
<mjacob> did it work at some point?
<arigato> no
<mjacob> i could translate it
<mjacob> but i got "out of sync: unexpected byte in log (at release_gil)" in revdb.py
<arigato> yes, kind of expected
<arigato> we need to review pypy/interpreter/reverse_debugging.py
<mjacob> ok nice, at least now i have a task for the sprint ;)
<arigato> yes
<arigato> :-)
<arigato> note that the first thing to try is to check a pypy2 translation
<arigato> I wouldn't be too surprized if it fails in the same way
<arigato> historically, that's how revdb-enabled versions of pypy failed when some details changed
<arigato> often
<arigato> ...more often than not, details like the Linux kernel suddenly randomizing address spaces, which I did not check against before; etc.
<mjacob> yes, i'm doing that right now; if it fails, i'm not sure whether i should try to fix it or i should go back to a known-good revision (which?)
<arigato> ah no, sorry
<arigato> I see there was a branch 'py3.5-reverse-debugger' that I merged at some point
<arigato> that should give a known-good revision
<arigato> though the problem might be external too, like the Linux kernel randomization issue
<mjacob> i see
<mjacob> especially on arch linux, which quickly gets a the newest kernel
<arigato> yes
<arigato> if necessary I can try on the same program as you: I have arch linux too, but long-term-support kernels
<mjacob> ok, i'll wait for the translation and report back
<mjacob> arigato: as first i tried translating it with default, but i get this error: https://paste.pound-python.org/show/CBvFscT1YxAZCu7JSLfD/
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5939 [mattip: force build, unicode-utf8-py3]
<mjacob> translating with "pypy rpython/bin/rpython -O2 --revdb --no-shared pypy/goal/targetpypystandalone.py --withoutmod-micronumpy"
<arigato> ah, these errors probably come from the gc-disable branch
<arigato> I bet they exist in any translation using --gc=boehm
<arigato> probably an easy fix
<mjacob> i'll try the py3.5-reverse-debugger branch in the meantime (my code works with python 2 and 3)
Zaab1t has quit [Quit: bye bye friends]
<mjacob> arigato: in the py3.5-reverse-debugger branch it works outside of a virtualenv, but inside i get the same "out of sync: unexpected byte in log (at release_gil)" error as before
<arigato> ah
<mjacob> when testing with a simple hello world script, the log file is 416K when run outside of a virtualenv and 392K when run inside the virtualenv
<mjacob> it works with -S (inside and outside)
<mjacob> how could i pinpoint the error?
<arigato> no clue...
<mjacob> the problem starts appearing after installing something in the virtualenv with 'pip install -e'
<arigato> I mean, not really "no clue", but it's rather that it's a quite hard question
<arigato> it means that what is put in the log file is unexpected
<mjacob> i'm trying to make a more minimal test case, that doesn't involve virtualenv at all
<arigato> that's probably not helping much
<arigato> it's like tracking a JIT bug: it doesn't help much to reduce your Python program (beyond helping by making it more easily runnable by others)
<mjacob> ok, what can we do? debug revdb with revdb? ;)
<arigato> first make sure to put away the .c files
<arigato> of the pypy with revdb built in
<arigato> there should be "revdb.c" in there, hack it to print more information and/or hack around with revdb.py to run the executable under gdb (of course, you need to recompile it with -g)
<arigato> it's a hard question in particular because of the way threads are handled
<arigato> pypy-revdb relies on the GIL to write in the log in a sane way
<arigato> but it needs to write information about thread switches (or more precisely the GIL being acquired by a different thread)
<kenaan> arigo default 30d8fded3b4f /: Support for revdb translation
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7213 [mattip: force build, unicode-utf8-py3]
themsay has quit [Ping timeout: 250 seconds]
themsay has joined #pypy