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 joined #pypy
jcea has quit [Quit: jcea]
jcea has joined #pypy
jcea has quit [Client Quit]
jcea has joined #pypy
jcea has quit [Client Quit]
jcea has joined #pypy
jcea has quit [Quit: jcea]
jcea has joined #pypy
jcea has quit [Client Quit]
jcea has joined #pypy
jcea has quit [Quit: jcea]
jcea has joined #pypy
jcea has quit [Ping timeout: 260 seconds]
jcea has joined #pypy
jcea has quit [Ping timeout: 260 seconds]
<tumbleweed> from more poking through test failures, it would be nice to get stdlib-2.7.16 landed. I had to cherry-pick a bunch of fixes to unit tests from cpython
<mgorny> tumbleweed: didn't you mean 3.7*?
<mattip> tumbleweed: :(
<mattip> dunno if I want to delay the release for that
<mattip> danchr: did you merge from the release 3.7 branch back to py3.7?
<mattip> why?
<mattip> also: what was the motivation for 1e201303cf39 ? Was there an issue it cleared up?
<mattip> it is a rather large change
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/8350 [mattip: force build, py3.7]
<bbot2> Started: http://buildbot.pypy.org/builders/own-win-x86-32/builds/2457 [mattip: force build, py3.7]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/5541 [mattip: force build, py3.7]
<danchr> mattip: not intentionally; I thought I took care to have everything in a topic, but maybe I screwed up
<danchr> oh, great, and the changes are published now
<danchr> goddammit
<danchr> I wasn't aware I even had privileges to publish changes?
<mattip> ok, mistakes happen
<mattip> (I broke things in a major way a few months ago doing something similar)
<bbot2> Failure: http://buildbot.pypy.org/builders/own-win-x86-32/builds/2457 [mattip: force build, py3.7]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/5541 [mattip: force build, py3.7]
<mattip> danchr: I will just back all the last commits out, ok?
<danchr> please do
<danchr> and thanks :)
<danchr> ISTR backing out a merge only to reapply it later is non-trivial, but I might remember wrong…
<mattip> I added a commit after the last accepted commit, so now there are two heads
<mattip> then I merged the heads, rejecting all the changes from the head with your commits
<mattip> danchr: I think we are reaching the conclusion that it would be better to avoid topic branches, even though heptapod supports them
<mattip> as you have discovered, they are confusing
<mattip> activating the extension also makes hg slower
<mattip> and as for using them as a playground on the repo:
<mattip> it is difficult if not impossible to kick a build of a topic branch
<tumbleweed> mattip: yeah, I found all the patches I needed, no urchency there
<mgorny> I wonder when we'll reach the conclusion that hg itself is confusing xP
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/8350 [mattip: force build, py3.7]
<arigato> Maybe something like that would help convince me that we can move to git without loosing all branch history
<mattip> so that would add a note to each commit which branch it is from?
<arigato> I guess so
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6025 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7217 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5221 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/5542 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/1395 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-aarch64/builds/665 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7217 [mattip: build release, release-pypy3.7-v7.x]
<antocuni> arigato: I kind of like the idea, but I think then we would still be missing the equivalent of "hg log -b" (although maybe it is possible to hack something around it)
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6025 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/1395 [mattip: build release, release-pypy3.7-v7.x]
oberstet has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-aarch64/builds/665 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5221 [mattip: build release, release-pypy3.7-v7.x]
<bbot2> Exception: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/5542 [mattip: build release, release-pypy3.7-v7.x]
jacob22 has quit [Read error: Connection reset by peer]
jacob22 has joined #pypy
<danchr> I hope my tomfoolery isn't the thing that causes you to migrate off of Mercurial — which I rather like and use a lot myself
<danchr> but since both topics and heptapod are relatively new and under active development — perhaps it's a failure or bug in their model? it would be nice if I couldn't push to certain branches or publish changesets
<danchr> that's essentially what I expected
<mattip> yeah, I am asking heptapod what happened. The default, py3.6 and py3.7 branches should be locked
fling has quit [Ping timeout: 240 seconds]
fling has joined #pypy
<tos9> antocuni: (I have no idea how well this'd work, so maybe it qualifies as "hacking something"), but yeah `git log` supports notes
<tos9> so if you have the branch in a note you can run like `git log --grep --notes whateverbranch` and that will match on what's in the notes contents.
<antocuni> ah, nice!
<tos9> (it of course will do dumb things though if the branch name is contained in the commit message of random other commits, so yeah may require slight additional thought)
<tos9> probably there's an option somewhere to tell it *not* to match the commit message but I don't know it off hand.
<antocuni> yeah sure, but it should work 99% of the times. Also, if you put a special tag like: "named-branch: foobar" in the notes, it becomes easy to grep for just that
<tos9> yup
jacob22 has quit [Read error: Connection reset by peer]
jacob22 has joined #pypy
wilbowma has quit [Ping timeout: 260 seconds]
wilbowma has joined #pypy
pmp-p has quit [Quit: No Ping reply in 180 seconds.]
pmp-p has joined #pypy
<mattip> the release has a bitbucket link to the LICENCSE file, but only when you do
<mattip> >>> license()
<mattip> I am releasing with that bug
<Cheery> Hi, I did only recently looked into functional programming runtimes, and I see there's bunch of things done here already.
<Cheery> there's the push/enter eval/apply operational semantics for STG
<Cheery> With GHC they found out, just use eval/apply, because the push/enter is not doing much.
<Cheery> but did that extend over to oJIT?
<simpson> I'm looking for the RPython Haskell example interpreter so I can point at that when answering, but I can't find it.
<simpson> The Bitbucket repository is gone.
<simpson> I don't think so; there used to be http://bitbucket.org/cfbolz/haskell-python and it showed off the core of a JIT-compatible Haskell-style lazy functional evaluator.
<mattip> you can see a backup of the repos https://bitbucket-archive.softwareheritage.org/projects/py.html
<mattip> if you search for "pypy/"
<mattip> ahh, under cfbolz
<mattip> simpson: you might want to reach out to cfbolz to restore that either under heptapod/pypy or somewhere else
<simpson> Cool, thanks.
<mattip> arigato: could you build the release for ppc64? I am starting to upload it to buildbot.pypy.org (under public_html/mirror/)
<Cheery> \o/ found the paper
<Cheery> Trace-based just-in-time compiler for Haskell with RPython
oberstet has quit [Quit: Leaving]
<mattip> release blog post preview
* mattip zzz
tos9_ has joined #pypy
tos9 has quit [Ping timeout: 272 seconds]