Hi Philip, Can we get a discussion with respect to Python 3.6? I see that you created a "py3.6" branch. However, the people funded by Mozilla (like me) are more interested in finishing a good 3.5.x version first. (I suppose it's up to discussion if we decide to go for 3.6 immediately, but I guess the answer is no.) That means we'll keep releasing 3.5 versions and won't look into 3.6 before next summer. It's unclear to me that it's worthwhile to start a parallel py3.6 branch right now, as it'll just be merging hell for the next 6 months. Well, I suppose it's your hell, so I can't complain on my own :-) Just to say, maybe your time would be better spent helping us with 3.5, instead of maintaining py3.6 when py3.5 is still fast-moving. A bientôt, Armin.
On Dec 24, 2016, at 1:54 AM, Armin Rigo <armin.rigo@gmail.com> wrote:
Hi Philip,
Can we get a discussion with respect to Python 3.6? I see that you created a "py3.6" branch. However, the people funded by Mozilla (like me) are more interested in finishing a good 3.5.x version first. (I suppose it's up to discussion if we decide to go for 3.6 immediately, but I guess the answer is no.)
That means we'll keep releasing 3.5 versions and won't look into 3.6 before next summer. It's unclear to me that it's worthwhile to start a parallel py3.6 branch right now, as it'll just be merging hell for the next 6 months. Well, I suppose it's your hell, so I can't complain on my own :-)
Hey, I’m not intending to do much more with it, I would rather help w/ 3.5 like you’re suggesting. In the past there’s always been others who were eager to hack on the latest 3.x, so somebody was bound to start this branch at some point anyway. I figured I’d do the work of the merge now, and carefully — we’ve unfortunately had some issues with this large 3.x vendor merge in the past =] I also got a quick look at 3.6 and the gratification of more closely chasing the head of cpython after all these years. — Philip Jenvey
Thank you very much on working towards 3.5 guys. As users we can forget about 3.6 for now since 3.5 gives a lot of improvment that most of us are looking for (asyn await and co ). Would like to see it released soon , PyPy 3.5 is only thing we are waiting , to move forward from python 2.7.x On Sun, Dec 25, 2016 at 12:47 AM Philip Jenvey <pjenvey@underboss.org> wrote:
On Dec 24, 2016, at 1:54 AM, Armin Rigo <armin.rigo@gmail.com> wrote:
Hi Philip,
Can we get a discussion with respect to Python 3.6? I see that you created a "py3.6" branch. However, the people funded by Mozilla (like me) are more interested in finishing a good 3.5.x version first. (I suppose it's up to discussion if we decide to go for 3.6 immediately, but I guess the answer is no.)
That means we'll keep releasing 3.5 versions and won't look into 3.6 before next summer. It's unclear to me that it's worthwhile to start a parallel py3.6 branch right now, as it'll just be merging hell for the next 6 months. Well, I suppose it's your hell, so I can't complain on my own :-)
Hey,
I’m not intending to do much more with it, I would rather help w/ 3.5 like you’re suggesting.
In the past there’s always been others who were eager to hack on the latest 3.x, so somebody was bound to start this branch at some point anyway. I figured I’d do the work of the merge now, and carefully — we’ve unfortunately had some issues with this large 3.x vendor merge in the past =]
I also got a quick look at 3.6 and the gratification of more closely chasing the head of cpython after all these years.
— Philip Jenvey _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
participants (3)
-
Armin Rigo -
Philip Jenvey -
Phyo Arkar