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
gracinet has quit [Quit: Leaving.]
CrazyPython has quit [Read error: Connection reset by peer]
fangerer_ has quit [Quit: Connection closed for inactivity]
gracinet has joined #pypy
gracinet has left #pypy [#pypy]
<plan_rich>
mattip: well, the case you sent me. it creates a virtualenv with the pypy built by the system. Unfortunate I do not know much about virtualenv to understand where the python executable generates the names virtualenv needs to operate.
<plan_rich>
could be that the names it looks up is the executable name. but then it is strange that it does not find pypy, because it is present in the folder
<mattip>
what version of virtualenv are you running?
<plan_rich>
20.0.4
<mattip>
maybe it is a problem with virtualenv>20 wich is from January and no other buildbot slave has hit that yet
<plan_rich>
ah, ok. I'll try that right now
<mattip>
on ubuntu 18.04, mine is 15.1.0 in /usr/bin/virtualenv
<plan_rich>
yes it worked. I guess one should create a ticket for that on the virtualenv tracker.
<mattip>
so the problem is `virtualenv -p pypy/virtualenv/bin/pypy target' ?
<mattip>
I guess we should try to dig a bit more to figure out what is going on. Maybe some symlink magic is failing
plan_rich_ has joined #pypy
<plan_rich_>
mattip: yes. I'll check if that happens for x86_64 as well, I think that is just an issue related to the s390x
plan_rich has quit [Ping timeout: 272 seconds]
plan_rich_ is now known as plan_rich
<plan_rich>
nope, works fine on x86_64.
<mattip>
:(
<plan_rich>
and it works on s390x if you download it from the buildbot fully packaged. There is something wrong with that executable that lies around in that specific build
<mattip>
:( :( :(
marky1991 has quit [Ping timeout: 268 seconds]
<plan_rich>
other strange thing that happens is that the test_infrastructure fails to import the module lib_pypy/_ctypes_test.py. On line 6 it imports cpyext and fails. After that it reports that '_ctypes_test' module is missing when it really fails to import cpyext
<plan_rich>
I suppose that ./pytest.py -k <testname> does not work right?