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
jcea has quit [Ping timeout: 268 seconds]
cfbolz has quit [Read error: Connection reset by peer]
cfbolz has joined #pypy
jaraco has quit [Read error: Connection reset by peer]
jaraco has joined #pypy
forgottenone has joined #pypy
dansan has quit [Ping timeout: 264 seconds]
trfl has quit [Remote host closed the connection]
dustinm has quit [Quit: Leaving]
trfl has joined #pypy
dustinm has joined #pypy
tsaka__ has quit [Ping timeout: 240 seconds]
glyph has quit [Quit: End of line.]
glyph has joined #pypy
jcea has joined #pypy
lritter has joined #pypy
<fijal> what is going on....
<mattip> maybe somehow your virtualenv in /home/fijal/.virtualenvs/pypy3 has a different lib_pypy path than /home/fijal/load/pypy-c-jit-101475-6dd03ceea326-linux64/?
<fijal> I don't know, installed newer pypy and seems ok
<fijal> is there any way I can find out what is causing "multiple versions of packages"?
<mattip> I don't see that message in the pastebin
<fijal> no, it's a different pastebin
<fijal> but I don't know wtf is the problm - it seems if I use old resolver, it does not find conflicts
<fijal> I don't know, but backtracking does not seem like a good idea to me
oberstet has joined #pypy
tsaka__ has joined #pypy
<LarstiQ> pip versions?
<LarstiQ> I've had to manually drop a newer pip in /usr/share/python-wheels
<fijal> what's the strategy dealing with manlylinux? how do you create the right set of wheels?
<fijal> mattip: do we know why this happens?
Dejan has joined #pypy
<fijal> ok, that's pypy3.6
<fijal> I think
<mattip> fijal: for dockers there is https://github.com/docker-library/pypy
<fijal> yeah Im using those, sort of
<mattip> for manylinux there is multibuild and cibuildwheel which use manylinux2010 images with pypy
<mattip> as for the missing PyPyUnicode_Check - no idea
<mattip> but it is a bad sign if even a pypy core dev cannot use pypy easily
<fijal> I can't use python easily, I think
<fijal> I have a failure (on pypy) and I can't get there, at all
<fijal> between pip being strange, ever changing dependency hell etc it all makes no sense to me
<fijal> mattip: I think pypy error is old pypy
<mattip> :(
<fijal> cryptography added to the mess as of last week too
<fijal> now you need a from-source-compiled rust compiler on a lot of linuxes
<fijal> I think if you work on software once a week, you spedn that time catching up on dependencies and nothing else?
<mattip> or just pin everything to an older version?
<exarkun> pin pin pin all the things
<exarkun> upgrade when you want to upgrade, not when a random dependency makes you upgrade
<fijal> exarkun: it's a bit hard
<fijal> but yeah I guess so
<fijal> it's a bit harder when the task at hand "make this run on pypy"
<fijal> and not "sort out the dependency hell"
<mattip> if you can deal with conda on x86_64, they have pretty good support for pypy37 these days
<mattip> I end up installing numpy/scipy/matplotlib from conda, and then pip installing the more esoteric stuff
jcea has quit [Ping timeout: 240 seconds]
sven- has joined #pypy
sven has quit [Ping timeout: 246 seconds]
sven- is now known as sven
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6232 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7492 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
oberstet has quit [Read error: Connection reset by peer]
<bbot2> Success: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7492 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
<bbot2> Success: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6232 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
activelow has joined #pypy
activelow has left #pypy [#pypy]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6233 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7493 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
oberstet has joined #pypy
jaraco has quit [Ping timeout: 260 seconds]
cfbolz has quit [Read error: Connection reset by peer]
cfbolz has joined #pypy
jaraco has joined #pypy
<bbot2> Success: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7493 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
<bbot2> Success: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6233 [Carl Friedrich Bolz-Tereick: force build, intbound-improvements-3]
jacob22 has joined #pypy
dmalcolm_ has joined #pypy
dmalcolm has quit [Ping timeout: 256 seconds]
jcea has joined #pypy
jacob22 has quit [Ping timeout: 256 seconds]
jacob22 has joined #pypy
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-64/builds/98 [Carl Friedrich Bolz-Tereick: force build, py3.7-hack-execution-count]
jacob22 has quit [Ping timeout: 272 seconds]
jacob22 has joined #pypy
forgottenone has quit [Remote host closed the connection]
lritter has quit [Ping timeout: 256 seconds]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-64/builds/98 [Carl Friedrich Bolz-Tereick: force build, py3.7-hack-execution-count]