[python-committers] [RELEASED] Python 3.4.0 release candidate 3

2014-03-10 Thread Larry Hastings
On behalf of the Python development team, I'm pleased to announce the third and final** release candidate of Python 3.4. This is a preview release, and its use is not recommended for production settings. Python 3.4 includes a range of improvements of the 3.x series, including hundreds of small

[python-committers] Brian Kearns for commit

2014-03-10 Thread Alex Gaynor
Hi all, I'd like to propose Brian Kearns for commit. He's been a committer on PyPy for about a year and a half now, and in particular he's done a bunch of "Python version" works: things like upgrading us from the 2.7.3 stdlib to the 2.7.6 stdlib, and py3k work. He's interested in having commit for

Re: [python-committers] Brian Kearns for commit

2014-03-10 Thread Guido van Rossum
I have nothing against Brian personally, but I have a process question: Has he previously gotten patches accepted to the stdlib, or is this a preemptive request? I think the usual route is to grant commit access after the stream of patches from a contributor has taken the form of a steady stream (o

Re: [python-committers] Brian Kearns for commit

2014-03-10 Thread Antoine Pitrou
On lun., 2014-03-10 at 16:02 -0700, Alex Gaynor wrote: > Hi all, > > > I'd like to propose Brian Kearns for commit. He's been a committer on > PyPy for about a year and a half now, and in particular he's done a > bunch of "Python version" works: things like upgrading us from the > 2.7.3 stdlib to

Re: [python-committers] Brian Kearns for commit

2014-03-10 Thread Antoine Pitrou
On mar., 2014-03-11 at 00:09 +0100, Antoine Pitrou wrote: > On lun., 2014-03-10 at 16:02 -0700, Alex Gaynor wrote: > > Hi all, > > > > > > I'd like to propose Brian Kearns for commit. He's been a committer on > > PyPy for about a year and a half now, and in particular he's done a > > bunch of "Py