Re: [python-committers] Can we delete https://hg.python.org/coding/cpython/?

2016-12-19 Thread Benjamin Peterson
Killed. On Mon, Dec 19, 2016, at 14:23, Brett Cannon wrote: > It's erroneously labeled as the "official python repo" and created by > some > stranger. > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman

[python-committers] Can we delete https://hg.python.org/coding/cpython/?

2016-12-19 Thread Brett Cannon
It's erroneously labeled as the "official python repo" and created by some stranger. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/cod

Re: [python-committers] Should I delay 3.5.3 and 3.4.6 by two weeks?

2016-12-19 Thread Antoine Pitrou
Le 19/12/2016 à 06:26, Larry Hastings a écrit : > > So, if you have an opinion, please vote for one of these three options: > > * Don't slip 3.5.3. and 3.4.6. > * Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0. > * Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to >

Re: [python-committers] [Python-Dev] Should I delay 3.5.3 and 3.4.6 by two weeks?

2016-12-19 Thread Brett Cannon
On Mon, 19 Dec 2016 at 06:29 Terry Reedy wrote: > On 12/19/2016 12:26 AM, Larry Hastings wrote: > > > > > > Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and > > 3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle" > > around the release. I expect a flood of a

Re: [python-committers] [Python-Dev] Should I delay 3.5.3 and 3.4.6 by two weeks?

2016-12-19 Thread Raymond Hettinger
> On Dec 18, 2016, at 9:26 PM, Larry Hastings wrote: > > So, if you have an opinion, please vote for one of these three options: > • Don't slip 3.5.3. and 3.4.6. > • Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0. > • Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the a