Re: [python-committers] autoconf 2.70

On 11/22/2016 08:16 PM, Ned Deily wrote: > On Nov 22, 2016, at 11:06, Xavier de Gaye wrote: >> The configure file on the default and 3.6 branches have been generated >> with autoconf 2.70 once again. This is annoying when you have to >> maintain patches to this configure file

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

Ok, thank you Raymond for checking. Victor Le 23 nov. 2016 05:25, "Raymond Hettinger" a écrit : > > > On Nov 22, 2016, at 6:57 AM, Victor Stinner > wrote: > > > > Should I revert these changes? > > I don't think reverting any of these

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

On 23 November 2016 at 06:40, Steve Dower wrote: > On 22Nov2016 1150, R. David Murray wrote: >> >> Being who we are (precisionist programmers), the inconsistency between >> "beta release cuts off features" and "last beta before RC cuts off >> non-release-critical fixes"

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

If we want the version to be PEP 440 compliant it'd be like 3.6rc1.dev0 or so if I remember correctly. Sent from my iPhone > On Nov 22, 2016, at 3:40 PM, Steve Dower wrote: > >> On 22Nov2016 1150, R. David Murray wrote: >> Being who we are (precisionist programmers),

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

On 22Nov2016 1150, R. David Murray wrote: Being who we are (precisionist programmers), the inconsistency between "beta release cuts off features" and "last beta before RC cuts off non-release-critical fixes" does produce some cognitive dissonance. I've seen the RC described as "the first beta

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

On Tue, 22 Nov 2016 13:47:35 -0500, Ned Deily wrote: > On Nov 22, 2016, at 12:59, Brett Cannon wrote: > > I think for me what made everything click was realizing that we used > > to say "until rc1 is cut, treat it as the beta phase", while Ned is > > saying

Re: [python-committers] autoconf 2.70

On Nov 22, 2016, at 11:06, Xavier de Gaye wrote: > The configure file on the default and 3.6 branches have been generated > with autoconf 2.70 once again. This is annoying when you have to > maintain patches to this configure file in order to build on a non > supported

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

On Nov 22, 2016, at 09:57, Victor Stinner wrote: > 2016-11-22 8:24 GMT+01:00 Ned Deily : >> OK, all of the release engineering for 3.6.0b4 is complete. The 3.6 branch >> in the cpython repo is now available again but, as noted, *only* for >> reviewed

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

On Tue, 22 Nov 2016 at 09:45 Ned Deily wrote: > On Nov 22, 2016, at 10:20, R. David Murray wrote: > > I'm sorry, but I find this confusing. It wasn't what I understood > > your previous email to mean, which means I didn't read it carefully > > enough and

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

On Nov 22, 2016, at 10:20, R. David Murray wrote: > I'm sorry, but I find this confusing. It wasn't what I understood > your previous email to mean, which means I didn't read it carefully > enough and saw it through a filter of my preconceptions. No problem! We are doing

Re: [python-committers] autoconf 2.70

The configure file on the default and 3.6 branches have been generated with autoconf 2.70 once again. This is annoying when you have to maintain patches to this configure file in order to build on a non supported platform. Xavier ___ python-committers

Re: [python-committers] New core developer: Xiang Zhang

Hi all, I am very glad and honored to join this community. Thanks everyone, especially Victor for his willingness to mentor me and Serhiy, always gives me a quick and thoughtful reply. Also apologize to those noised by me due to my poor skills and English. Best Regards Xiang Zhang

Re: [python-committers] New core developer: Xiang Zhang

On 22 November 2016 at 15:01, Eric V. Smith wrote: > On 11/22/16 9:21 AM, Victor Stinner wrote: >> >> * python-committers: he subscribed to python-committers. Can someone >> check if you got it (and approve it)? His email adddress is >> angwe...@126.com > > > I didn't see a

Re: [python-committers] New core developer: Xiang Zhang

On 11/22/16 9:21 AM, Victor Stinner wrote: * python-committers: he subscribed to python-committers. Can someone check if you got it (and approve it)? His email adddress is angwe...@126.com I didn't see a request, so I just subscribed him. Welcome aboard Xiang! Yes, welcome! Eric.

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

Hi, 2016-11-22 8:24 GMT+01:00 Ned Deily : > OK, all of the release engineering for 3.6.0b4 is complete. The 3.6 branch > in the cpython repo is now available again but, as noted, *only* for reviewed > release critical fixes appropriate for the 3.6.0 final and for final 3.6.0

[python-committers] New core developer: Xiang Zhang

Hi, We have a new core developer today, Xiang Zhang! He comes from China and is already very active in various area of the CPython soure code. He just got his commit bit. * commit bit: Brett added Xiang's key. Xiang already pushed a test commit, https://hg.python.org/test/rev/530f0afa8072 *