Dnia 2014-01-14, o godz. 14:27:03 Marien Zwart napisał(a): > On the other hand (at least in the short term) running an older PyPy > isn't something I'd expect a lot of people to do: running the latest > and greatest is usually beneficial, not just for features but also for > better performance and fewer bugs. Chances are most users will either > fix their code to work with latest PyPy, or run it under CPython for > compatibility. That seems like an argument not to keep PyPy slotting > if it's awkward to implement. Oh, this reminds me of yet another argument. We're basically supporting only one version of PyPy at a time. This makes the current workflow like: 1. add new slot, 2. add PYTHON_COMPAT for new slot, 3. remove old slot. So the two versions are really supported for a short time. I think we may instead use the following work flow: 1. add new PyPy masked, 2. test packages, 3. unmask new PyPy :). This would also mean that we'd be able to avoid removing old versions of PyPy as fast as we do now. -- Best regards, Michał Górny