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
themsay has joined #pypy
themsay has quit [Read error: Connection reset by peer]
xcm has quit [Ping timeout: 268 seconds]
themsay has joined #pypy
antocuni has quit [Ping timeout: 268 seconds]
xcm has joined #pypy
themsay has quit [Read error: Connection reset by peer]
themsay has joined #pypy
themsay has quit [Ping timeout: 268 seconds]
xcm has quit [Read error: Connection reset by peer]
xcm has joined #pypy
demonimin has quit [Quit: bye]
demonimin has joined #pypy
lritter has joined #pypy
xcm has quit [Ping timeout: 244 seconds]
xcm has joined #pypy
_whitelogger has joined #pypy
PileOfDirt has quit [Remote host closed the connection]
lritter has quit [Ping timeout: 250 seconds]
lritter has joined #pypy
<mattip> njs: the core is not in /var/crash either, even though other core dumps are there
<njs> check ulimit -c? otherwise idk
<mattip> I issued a PR https://github.com/scipy/scipy/pull/9601 with PYPY_GC_MAX, let's see if that improves the situation
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5868 [mattip: force build, unicode-utf8]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7143 [mattip: force build, unicode-utf8]
dddddd has quit [Remote host closed the connection]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7143 [mattip: force build, unicode-utf8]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5868 [mattip: force build, unicode-utf8]
_whitelogger_ has joined #pypy
_whitelogger has quit [Ping timeout: 250 seconds]
dmalcolm has joined #pypy
_whitelogger has joined #pypy
jacob22__ has quit [Quit: Konversation terminated!]
_whitelogger has joined #pypy
antocuni has joined #pypy
hastake has quit [Ping timeout: 244 seconds]
hastake has joined #pypy
lritter has quit [Ping timeout: 250 seconds]
antocuni has quit [Ping timeout: 240 seconds]
lesshaste has joined #pypy
<lesshaste> hi all
dddddd has joined #pypy
_whitelogger has joined #pypy
Curi0 has joined #pypy
<Curi0> Hi I built PyPy3 from source and installed pip but I'm having problems installing packages. Installing aiohttp gives me EOFError
<mattip> Curi0 can you paste the error to a pastbin/gist ?
<mattip> we recommend you use a virtualenv to make sure you do not pick up cpytohn headers/libraries
<Curi0> i'm not using virtualenv
themsay has joined #pypy
<mattip> pypy3 -mpip install aiohttp works for me https://paste.ubuntu.com/p/7d48QTWNpS/
<mattip> this is on ubuntu 18.06 with pypy3.5.3 version 6.0.0
<Curi0> i have ubuntu 18.04
<Curi0> i built mine from source
<mattip> right, s/18.06/18.04/ sorry
<mattip> what does hg id show, which commit?
<LarstiQ> hmm, that load_grammar looks familiar
<LarstiQ> Curi0: https://github.com/jaraco/irc/issues/33 e.g., you could try putting the pickle in place yourself
<LarstiQ> or perhaps use a newer pip?
<Curi0> lastmikoi, i used the get-pip script
<Curi0> mattip, latest stable archive
<mattip> after building, you need to do
<mattip> pypy3-c -mensurepip
<mattip> pypy3-c -mpip install --upgrade pip setuptools
<mattip> what is "stable archive"?
<Curi0> mattip, the source download on the website
<Curi0> the tar or whatever
<mattip> ahh, ok
<Curi0> mattip, it says already up to date
<mattip> strange. I don't think I did anything beyond updating pip, setuptools to my virtualenv
<Curi0> i ran the get-pip script
<Curi0> maybe that did something
<mattip> well, a virtualenv is highly advised, it solves many permission problems
<Curi0> ill try that
<Curi0> mattip, does aiohttp work for you ?
<Curi0> ive installed some other packages without errors but aiohttp gives eoferror
<Curi0> brb i have a bouncer btw
Zaab1t has joined #pypy
<agronholm> how close is pypy3 to py3.6 compatibility now? the wiki page hasn't been updated since september, but I see no more test failures on the bug tracker: http://buildbot.pypy.org/summary?builder=pypy-c-jit-linux-x86-64&branch=py3.6
<mattip> agronholm: the test results are empty because we delete old ones after a while
<mattip> not because the tests all pass
<agronholm> ok, what should I be looking at then?
<agronholm> I'd hate to bother people here with requests for updates
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/6186 [mattip: force build, py3.5]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7144 [mattip: force build, py3.5]
<bbot2> Started: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1915 [mattip: force build, py3.5]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-s390x/builds/1140 [mattip: force build, py3.5]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/4291 [mattip: force build, py3.5]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/954 [mattip: force build, py3.5]
<bbot2> Started: http://buildbot.pypy.org/builders/rpython-linux-x86-32/builds/109 [mattip: force build, py3.5]
<cfbolz> agronholm: we should start a build on the branch to see the current status
<agronholm> 3.6 is the right branch, yes?
<cfbolz> py3.6
<agronholm> right
<cfbolz> just a sec, let me merge in py3.5 first
<cfbolz> agronholm: it's going to take some time, mattip is occupying all the builders right now ;-)
<cfbolz> agronholm: I think this page is still sort of accurate: https://bitbucket.org/pypy/pypy/wiki/Status%20of%20PyPy3%20support%20for%203.6
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-app-level-linux-x86-64/builds/3971 [Carl Friedrich Bolz-Tereick: force build, py3.6]
<agronholm> that would mean...no progress since september? :/
<cfbolz> agronholm: yes, that's accurate
<agronholm> ok, thanks for the info
<cfbolz> nobody is actively working on 3.6, I fear
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5870 [Carl Friedrich Bolz-Tereick: force build, py3.6]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-app-level-linux-x86-64/builds/3971 [Carl Friedrich Bolz-Tereick: force build, py3.6]
Zaab1t has quit [Quit: bye bye friends]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7144 [mattip: force build, py3.5]
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7145 [Carl Friedrich Bolz-Tereick: force build, py3.6]
themsay has quit [Ping timeout: 245 seconds]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/5870 [Carl Friedrich Bolz-Tereick: force build, py3.6]
<bbot2> Success: http://buildbot.pypy.org/builders/rpython-linux-x86-32/builds/109 [mattip: force build, py3.5]
<mattip> ahh, whoops, I meant to start py3.6 not py3.5
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-32/builds/6186 [mattip: force build, py3.5]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/7145 [Carl Friedrich Bolz-Tereick: force build, py3.6]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/4291 [mattip: force build, py3.5]
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
jacob22__ has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-s390x/builds/1140 [mattip: force build, py3.5]
<mattip> ronan: any idea about the new datetime test failures on py3.5? Is a newly exposed pypy bug or a testing issue?
<ronan> I think it's real bugs
<ronan> probably differences between the Python datetime and C _datetime
<ronan> on py3 we use stdlib datetime, but not on py2
<mattip> ok, tomorrow
<ronan> mattip: I wonder if we should have a lib_pypy/_datetime.py ... It seems a bit silly, but hacking lib-python datetime too much isn't ideal either
<mattip> right, it would be nice to figure out what the root cause is. Do we have a different int/uint somewhere?
* mattip off
speeder39_ has joined #pypy
<tos9> cfbolz: The Dusseldorf sprint is still on I assume?
<cfbolz> tos9: yes (and I really really should post an official announcement)
<tos9> Cool.
<tos9> Will likely try to make a few days (and trying to encourage one or two people from my team to stop in as well).
<cfbolz> Cool
<cfbolz> tos9: which team is that?
<tos9> cfbolz: Er, work team, sorry.
<tos9> (Who I'd love to learn a bit about internals.)
<cfbolz> tos9: which company is that?
<tos9> cfbolz: Now it's Deloitte.
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
jcea has joined #pypy
Sigyn has left #pypy ["Leaving the channel (no spam or action taken for 30 days.) /invite Sigyn #pypy again if needed"]
<bbot2> Failure: http://buildbot.pypy.org/builders/own-win-x86-32/builds/1915 [mattip: force build, py3.5]