state of pypy 3.6 support

Hi all, Matti asked in an issue what the state of PyPy 3.6 support is, and whether we're close to an alpha: https://bitbucket.org/pypy/pypy/issues/2849/syntax-bug-for-keyword-only-argu... Since that's a strange place to have this discussion, I thought I'd move it here. Armin replied: "what I fear is that we didn't start seriously on the infinite list of small new things in 3.6. If that's true, then not close at all. It makes me wonder if we shouldn't do a "3.(5+1/2)" where we take the few major new things from 3.6 (which are already implemented in the 3.6 branch as far as I can tell) and release that. I guess they're all syntax tricks so they could all be backported without trouble." I am not quite so pessimistic. I agree that we implemented most of the big visible features and also I agree that there are quite a few details left. However, I think if a few people pushed for a couple for days, we could end up in a pretty decent state. I tried to classify the remaining problems here: https://bitbucket.org/pypy/pypy/wiki/Status%20of%20PyPy3%20support%20for%203... I will try to slowly chip away at some of these, but given my still limited time to work right now I'd need some help. Maybe we should have a dedicated "finish 3.6 virtual sprint" or something? What do others think? Cheers, Carl Friedrich

Maybe we should have a dedicated "finish 3.6 virtual sprint" or something? Thanks for shepherding this forward. A virtual sprint sounds like a good idea to get some momentum going. Would August be a good time or are
On 17/06/18 00:48, Carl Friedrich Bolz-Tereick wrote: people on holiday? Another thing to thnk about is that we target 3.6.1 right now, I don't know if there is a strong reason to already target a more advanced 3.6 for an alpha release. Matti
participants (2)
-
Carl Friedrich Bolz-Tereick
-
Matti Picus