Fix typo on PYPY version

[humitos]

Just a typo

[bebehei]

docker build . still failing though. What are your testing methods!?

[humitos]

@bebehei testing a docker image of ~7gb is hard if you don't have a good internet connection (and disk space!). Feel free to fix it properly or, considering that you already ran that command, share the feedback to know where it breaks. Thanks!

[bebehei]

@humitos I agree with you. While writing my PRs, my only system available built the image in a full hour. Testing it was a PITA. I have to run docker image prune regularly. Your own situation might be much worse.

But this is not how bad one's situation is. This is about enforcing minimal functionality in a project.

There's no problem, if things go south in a PR. I for myself pushed to PRs this week, which also didn't even compile. I made the same mistakes this week. Sometimes I even push untested to a PR on purpose, if the project is too big. So I push to my PR until CI gives a green checkmark.

But what freaks me out: There's a PR, which gets approved and merged onto the master branch while nobody has ever even checked it out and attempted to build it. It didn't build at all.

And no, in times where techniques to avoid this are broadly available, the excuse "I haven't got a beefy machine" isn't valid.

Feel free to fix it properly or, considering that you already ran that command, share the feedback to know where it breaks. Thanks!

I expected you did that by yourself. I'd definitely would have shared the feedback. Now that I'm knowing the circumstances, I would have reacted otherwise, sorry.

I propose you merge #96 (which also reverts your faulty commit). And then rework your PR #93 until it builds successfully. Just do a force push and you won't annoy anyone with push emails. So at the end of the day, everything will turn out fine.

If you care about the "wasted" build time on Travis: You're maintaining the basis of one of the biggest open source projects. 20 Minutes build time shouldn't matter in this case.