In that case, it would change the Python result dramatically as well.
But I don't think it would be fair: I use Python a lot, and if it's for scripting, you are happy with the fact it's very easy to write. However, it's slow to start, and you pay that each time you run the script.
To me, it makes sense in this exercice, which is heavily leaning toward scripting, we see the price of the VM start in the overall profiling.
Otherwise, let's use pypy, warm it up, a few 1000 times, and you may get closer to Go times.
But I don't think it would be fair: I use Python a lot, and if it's for scripting, you are happy with the fact it's very easy to write. However, it's slow to start, and you pay that each time you run the script.
To me, it makes sense in this exercice, which is heavily leaning toward scripting, we see the price of the VM start in the overall profiling.
Otherwise, let's use pypy, warm it up, a few 1000 times, and you may get closer to Go times.
But we don't use pypy for scripting.