From ncoghlan at gmail.com  Sun Feb  2 02:02:19 2014
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Sun, 2 Feb 2014 11:02:19 +1000
Subject: [python-committers] PEP 450: Commit access for Steven D'Aprano?
Message-ID: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>

When PEP 450 (the statistics module) was accepted, it looks like we
missed the step of granting Steven commit access for module
maintenance purposes. We should probably fix that :)

I'm happy to handle the task of bringing Steven up to speed on the
mechanics of contributing directly (and there's always the option of
pinging core-mentorship at python.org with any specific questions).

Steven: http://docs.python.org/devguide/coredev.html

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From guido at python.org  Sun Feb  2 02:03:31 2014
From: guido at python.org (Guido van Rossum)
Date: Sat, 1 Feb 2014 17:03:31 -0800
Subject: [python-committers] PEP 450: Commit access for Steven D'Aprano?
In-Reply-To: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
References: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
Message-ID: <CAP7+vJJHeB4uWXE_VX=0SdV0qTb_SMwBYphAZ1MAz1H2zwcuaA@mail.gmail.com>

+1


On Sat, Feb 1, 2014 at 5:02 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:

> When PEP 450 (the statistics module) was accepted, it looks like we
> missed the step of granting Steven commit access for module
> maintenance purposes. We should probably fix that :)
>
> I'm happy to handle the task of bringing Steven up to speed on the
> mechanics of contributing directly (and there's always the option of
> pinging core-mentorship at python.org with any specific questions).
>
> Steven: http://docs.python.org/devguide/coredev.html
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
>



-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140201/2cc321cc/attachment.html>

From tjreedy at udel.edu  Sun Feb  2 03:34:55 2014
From: tjreedy at udel.edu (Terry Reedy)
Date: Sat, 01 Feb 2014 21:34:55 -0500
Subject: [python-committers] PEP 450: Commit access for Steven D'Aprano?
In-Reply-To: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
References: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
Message-ID: <52EDAECF.5060609@udel.edu>

On 2/1/2014 8:02 PM, Nick Coghlan wrote:
> When PEP 450 (the statistics module) was accepted, it looks like we
> missed the step of granting Steven commit access for module
> maintenance purposes. We should probably fix that :)

If we do, he might get sucked into working on other things ;-).

Seriously, he loves and understands Python and has made numerous helpful 
and careful posts, mindful of details, to python-list for years (and 
perhaps tutor-list also).

+1

> I'm happy to handle the task of bringing Steven up to speed on the
> mechanics of contributing directly (and there's always the option of
> pinging core-mentorship at python.org with any specific questions).
>
> Steven: http://docs.python.org/devguide/coredev.html

I am willing to help anyone starting on Windows, or with TortoiseHG and 
its Workbench gui on any system.

Terry


From ethan at stoneleaf.us  Sun Feb  2 05:10:59 2014
From: ethan at stoneleaf.us (Ethan Furman)
Date: Sat, 01 Feb 2014 20:10:59 -0800
Subject: [python-committers] PEP 450: Commit access for Steven D'Aprano?
In-Reply-To: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
References: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
Message-ID: <52EDC553.2050808@stoneleaf.us>

On 02/01/2014 05:02 PM, Nick Coghlan wrote:
> When PEP 450 (the statistics module) was accepted, it looks like we
> missed the step of granting Steven commit access for module
> maintenance purposes. We should probably fix that :)

+1

--
~Ethan~

From eliben at gmail.com  Sun Feb  2 16:35:38 2014
From: eliben at gmail.com (Eli Bendersky)
Date: Sun, 2 Feb 2014 07:35:38 -0800
Subject: [python-committers] PEP 450: Commit access for Steven D'Aprano?
In-Reply-To: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
References: <CADiSq7fqZ5H0ZwPV2fJbzEJ5ZU1aqdDq=vc9HaJaRJNduPUyow@mail.gmail.com>
Message-ID: <CAF-Rda8+dKyt8yoBV3KtOZ4hqwKrR21Mogcd8AZhNv2GsMKtKw@mail.gmail.com>

On Sat, Feb 1, 2014 at 5:02 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:

> When PEP 450 (the statistics module) was accepted, it looks like we
> missed the step of granting Steven commit access for module
> maintenance purposes. We should probably fix that :)
>
> I'm happy to handle the task of bringing Steven up to speed on the
> mechanics of contributing directly (and there's always the option of
> pinging core-mentorship at python.org with any specific questions).
>
> Steven: http://docs.python.org/devguide/coredev.html
>

I'm surprised he's not a committer already; I was sure he was.

+1

Eli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140202/9df086fa/attachment.html>

From yselivanov.ml at gmail.com  Mon Feb  3 18:03:00 2014
From: yselivanov.ml at gmail.com (Yury Selivanov)
Date: Mon, 03 Feb 2014 12:03:00 -0500
Subject: [python-committers] review links
Message-ID: <52EFCBC4.1010207@gmail.com>

Hello,

Another quick infrastructure question (is this the right list, btw?):
I don't see 'review' links for some patches. Like in issue #14911,
Kristj?n uploaded two patches, same day, almost same time, and I
see a review link only for one of them.

Screenshot: http://goo.gl/HK2oer

Thanks,
Yury

From guido at python.org  Mon Feb  3 18:16:17 2014
From: guido at python.org (Guido van Rossum)
Date: Mon, 3 Feb 2014 09:16:17 -0800
Subject: [python-committers] review links
In-Reply-To: <52EFCBC4.1010207@gmail.com>
References: <52EFCBC4.1010207@gmail.com>
Message-ID: <CAP7+vJ+CRrdWm5Q4iDAV2yE41_kEHbP66vHVOk+j1L7PyvJHMw@mail.gmail.com>

IIRC the review link only appears if the patch applies cleanly.


On Mon, Feb 3, 2014 at 9:03 AM, Yury Selivanov <yselivanov.ml at gmail.com>wrote:

> Hello,
>
> Another quick infrastructure question (is this the right list, btw?):
> I don't see 'review' links for some patches. Like in issue #14911,
> Kristj?n uploaded two patches, same day, almost same time, and I
> see a review link only for one of them.
>
> Screenshot: http://goo.gl/HK2oer
>
> Thanks,
> Yury
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
>



-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140203/a87e5eb8/attachment.html>

From solipsis at pitrou.net  Mon Feb  3 18:20:14 2014
From: solipsis at pitrou.net (Antoine Pitrou)
Date: Mon, 03 Feb 2014 18:20:14 +0100
Subject: [python-committers] review links
In-Reply-To: <CAP7+vJ+CRrdWm5Q4iDAV2yE41_kEHbP66vHVOk+j1L7PyvJHMw@mail.gmail.com>
References: <52EFCBC4.1010207@gmail.com>
 <CAP7+vJ+CRrdWm5Q4iDAV2yE41_kEHbP66vHVOk+j1L7PyvJHMw@mail.gmail.com>
Message-ID: <1391448014.2336.0.camel@fsol>

On lun., 2014-02-03 at 09:16 -0800, Guido van Rossum wrote:
> IIRC the review link only appears if the patch applies cleanly.

And only if it applies cleanly on the default branch, IIRC :-)

Regards

Antoine.




From yselivanov.ml at gmail.com  Mon Feb  3 18:24:56 2014
From: yselivanov.ml at gmail.com (Yury Selivanov)
Date: Mon, 03 Feb 2014 12:24:56 -0500
Subject: [python-committers] review links
In-Reply-To: <1391448014.2336.0.camel@fsol>
References: <52EFCBC4.1010207@gmail.com>
 <CAP7+vJ+CRrdWm5Q4iDAV2yE41_kEHbP66vHVOk+j1L7PyvJHMw@mail.gmail.com>
 <1391448014.2336.0.camel@fsol>
Message-ID: <52EFD0E8.90709@gmail.com>

OK, thank you.

Are you sure it's the right thing to do? I.e. a user can create a
patch, ensure that it applies cleanly, and while he uploads it,
someone pushes to the repo. No 'review' link, no notification.

Wouldn't it make sense to always show the review link, and let
the user to resolve the conflicts if there are any?

Yury

On 2/3/2014, 12:20 PM, Antoine Pitrou wrote:
> On lun., 2014-02-03 at 09:16 -0800, Guido van Rossum wrote:
>> IIRC the review link only appears if the patch applies cleanly.
> And only if it applies cleanly on the default branch, IIRC :-)
>
> Regards
>
> Antoine.
>
>
>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers


From zachary.ware+pycommit at gmail.com  Mon Feb  3 18:25:10 2014
From: zachary.ware+pycommit at gmail.com (Zachary Ware)
Date: Mon, 3 Feb 2014 11:25:10 -0600
Subject: [python-committers] review links
In-Reply-To: <52EFCBC4.1010207@gmail.com>
References: <52EFCBC4.1010207@gmail.com>
Message-ID: <CAKJDb-Pt+25oUYzT-v4nkb62sqwmuKw8wP8GxszteH3mNejPUA@mail.gmail.com>

On Mon, Feb 3, 2014 at 11:03 AM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
> Hello,
>
> Another quick infrastructure question (is this the right list, btw?):

Core-mentorship is another good candidate.

> I don't see 'review' links for some patches. Like in issue #14911,
> Kristj?n uploaded two patches, same day, almost same time, and I
> see a review link only for one of them.

As was recently explained to me, patches created in 'git' format (`hg
diff --git`) will show a review link only if they apply cleanly to
default branch (so '--git' 2.7 patches will never show a review link
unless it just happens to apply to default as well).  Patches created
without '--git' give the revision they're applied to, so as long as
they apply cleanly to that revision, they'll show a review link no
matter the branch.

--
Zach

From brett at python.org  Mon Feb  3 18:38:57 2014
From: brett at python.org (Brett Cannon)
Date: Mon, 3 Feb 2014 12:38:57 -0500
Subject: [python-committers] review links
In-Reply-To: <52EFCBC4.1010207@gmail.com>
References: <52EFCBC4.1010207@gmail.com>
Message-ID: <CAP1=2W4FRNJ=z3u1OnH8KLBbHednPHc4Z=NFwU5sTt6sqmx-6Q@mail.gmail.com>

On Mon, Feb 3, 2014 at 12:03 PM, Yury Selivanov <yselivanov.ml at gmail.com>wrote:

> Hello,
>
> Another quick infrastructure question (is this the right list, btw?):
>

There is always the meta bug tracker at
http://psf.upfronthosting.co.za/roundup/meta/ for tracker issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140203/7bdd7487/attachment.html>

From greg at krypto.org  Mon Feb  3 20:47:48 2014
From: greg at krypto.org (Gregory P. Smith)
Date: Mon, 3 Feb 2014 11:47:48 -0800
Subject: [python-committers] review links
In-Reply-To: <1391448014.2336.0.camel@fsol>
References: <52EFCBC4.1010207@gmail.com>
 <CAP7+vJ+CRrdWm5Q4iDAV2yE41_kEHbP66vHVOk+j1L7PyvJHMw@mail.gmail.com>
 <1391448014.2336.0.camel@fsol>
Message-ID: <CAGE7PNLTqK_LnJpSR9OqVvLcFugZRhA0DNrqWyaSn+jkARJEPg@mail.gmail.com>

actually if your patch contains

"diff -r f4377699fd47 Lib/test/test_zipimport.py"

lines prior to the --- line as hg diff can emit, it'll do the right thing
and show the review against the version of the file listed (or at least
against it's branch head? that's an example taken from 3.3 for a patch that
most definitely does not apply cleanly to default||3.4)

-gps



On Mon, Feb 3, 2014 at 9:20 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:

> On lun., 2014-02-03 at 09:16 -0800, Guido van Rossum wrote:
> > IIRC the review link only appears if the patch applies cleanly.
>
> And only if it applies cleanly on the default branch, IIRC :-)
>
> Regards
>
> Antoine.
>
>
>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140203/43318965/attachment-0001.html>

From zachary.ware+pycommit at gmail.com  Thu Feb  6 22:52:04 2014
From: zachary.ware+pycommit at gmail.com (Zachary Ware)
Date: Thu, 6 Feb 2014 15:52:04 -0600
Subject: [python-committers] Buildbot issues?
Message-ID: <CAKJDb-MPEa6z59xzPvU7A+noDAEnioui76Y=FvhyAoBQucDM8g@mail.gmail.com>

Hi all,

Just got this output from pushing a commit:

"""
pushing to ssh://hg at hg.python.org/cpython
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: buildbot: change(s) NOT sent, something went wrong:
remote: buildbot: [Failure instance: Traceback (failure with no frames): <class
'twisted.internet.error.ConnectError'>: An error occurred while connecting: 113:
 No route to host.
remote: buildbot: ]
remote: sent email to roundup at report at bugs.python.org
remote: notified python-checkins at python.org of incoming changeset c964b6b83720
"""

Trying to load buildbot.python.org timed out as well.  Has the fleet
sailed away?

--
Zach

From mal at egenix.com  Fri Feb  7 09:55:52 2014
From: mal at egenix.com (M.-A. Lemburg)
Date: Fri, 07 Feb 2014 09:55:52 +0100
Subject: [python-committers] Buildbot issues?
In-Reply-To: <CAKJDb-MPEa6z59xzPvU7A+noDAEnioui76Y=FvhyAoBQucDM8g@mail.gmail.com>
References: <CAKJDb-MPEa6z59xzPvU7A+noDAEnioui76Y=FvhyAoBQucDM8g@mail.gmail.com>
Message-ID: <52F49F98.7050300@egenix.com>

On 06.02.2014 22:52, Zachary Ware wrote:
> Hi all,
> 
> Just got this output from pushing a commit:
> 
> """
> pushing to ssh://hg at hg.python.org/cpython
> searching for changes
> remote: adding changesets
> remote: adding manifests
> remote: adding file changes
> remote: added 1 changesets with 1 changes to 1 files
> remote: buildbot: change(s) NOT sent, something went wrong:
> remote: buildbot: [Failure instance: Traceback (failure with no frames): <class
> 'twisted.internet.error.ConnectError'>: An error occurred while connecting: 113:
>  No route to host.
> remote: buildbot: ]
> remote: sent email to roundup at report at bugs.python.org
> remote: notified python-checkins at python.org of incoming changeset c964b6b83720
> """
> 
> Trying to load buildbot.python.org timed out as well.  Has the fleet
> sailed away?

Probably just a temporary network/DNS failure. It seems to work fine
now.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Feb 07 2014)
>>> Python Projects, Consulting and Support ...   http://www.egenix.com/
>>> mxODBC.Zope/Plone.Database.Adapter ...       http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
2014-01-28: Released eGenix pyOpenSSL 0.13.3 ...  http://egenix.com/go52

::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/

From solipsis at pitrou.net  Fri Feb  7 14:24:34 2014
From: solipsis at pitrou.net (Antoine Pitrou)
Date: Fri, 07 Feb 2014 14:24:34 +0100
Subject: [python-committers] Buildbot issues?
In-Reply-To: <52F49F98.7050300@egenix.com>
References: <CAKJDb-MPEa6z59xzPvU7A+noDAEnioui76Y=FvhyAoBQucDM8g@mail.gmail.com>
 <52F49F98.7050300@egenix.com>
Message-ID: <1391779474.2296.0.camel@fsol>

On ven., 2014-02-07 at 09:55 +0100, M.-A. Lemburg wrote:
> > 
> > Trying to load buildbot.python.org timed out as well.  Has the fleet
> > sailed away?
> 
> Probably just a temporary network/DNS failure. It seems to work fine
> now.

According to infrastructure, there had been a kernel panic. The VM has
been restarted.

Regards

Antoine.



From georg at python.org  Mon Feb 10 21:55:40 2014
From: georg at python.org (Georg Brandl)
Date: Mon, 10 Feb 2014 21:55:40 +0100
Subject: [python-committers] [RELEASED] Python 3.3.4
Message-ID: <52F93CCC.70304@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On behalf of the Python development team, I'm very happy to announce
the release of Python 3.3.4.

Python 3.3.4 includes several security fixes and over 120 bug fixes
compared to the Python 3.3.3 release.

This release fully supports OS X 10.9 Mavericks.  In particular, this
release fixes an issue that could cause previous versions of Python to
crash when typing in interactive mode on OS X 10.9.

Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x.  In total, almost 500 API items
are new or improved in Python 3.3.  For a more extensive list of
changes in the 3.3 series, see

    http://docs.python.org/3.3/whatsnew/3.3.html

To download Python 3.3.4 visit:

    http://www.python.org/download/releases/3.3.4/


This is a production release, please report any bugs to

     http://bugs.python.org/


Enjoy!

- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.3's contributors)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlL5PMwACgkQN9GcIYhpnLCv4wCePNVqwsOYCHdJBix2bKk4PNpK
GBoAnRML2x6obCssnUJe5xwuUZYw8ZSY
=+/Nz
-----END PGP SIGNATURE-----

From larry at hastings.org  Tue Feb 11 08:43:15 2014
From: larry at hastings.org (Larry Hastings)
Date: Mon, 10 Feb 2014 23:43:15 -0800
Subject: [python-committers] [RELEASED] Python 3.4.0 release candidate 1
Message-ID: <52F9D493.6090100@hastings.org>


On behalf of the Python development team, I'm delighted to announce
the first 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 improvements and bug fixes.  Major new features and
changes in the 3.4 release series include:

* PEP 428, a "pathlib" module providing object-oriented filesystem paths
* PEP 435, a standardized "enum" module
* PEP 436, a build enhancement that will help generate introspection
            information for builtins
* PEP 442, improved semantics for object finalization
* PEP 443, adding single-dispatch generic functions to the standard library
* PEP 445, a new C API for implementing custom memory allocators
* PEP 446, changing file descriptors to not be inherited by default
            in subprocesses
* PEP 450, a new "statistics" module
* PEP 451, standardizing module metadata for Python's module import system
* PEP 453, a bundled installer for the *pip* package manager
* PEP 454, a new "tracemalloc" module for tracing Python memory allocations
* PEP 456, a new hash algorithm for Python strings and binary data
* PEP 3154, a new and improved protocol for pickled objects
* PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O

Python 3.4 is now in "feature freeze", meaning that no new features will be
added.  The final release is projected for mid-March 2014.


To download Python 3.4.0rc1 visit:

     http://www.python.org/download/releases/3.4.0/


Please consider trying Python 3.4.0rc1 with your code and reporting any
new issues you notice to:

      http://bugs.python.org/


Enjoy!

--
Larry Hastings, Release Manager
larry at hastings.org
(on behalf of the entire python-dev team and 3.4's contributors)

From ethan at stoneleaf.us  Tue Feb 11 10:01:38 2014
From: ethan at stoneleaf.us (Ethan Furman)
Date: Tue, 11 Feb 2014 01:01:38 -0800
Subject: [python-committers] [RELEASED] Python 3.4.0 release candidate 1
In-Reply-To: <52F9D493.6090100@hastings.org>
References: <52F9D493.6090100@hastings.org>
Message-ID: <52F9E6F2.40907@stoneleaf.us>

On 02/10/2014 11:43 PM, Larry Hastings wrote:
>
> On behalf of the Python development team, I'm delighted to announce
> the first release candidate of Python 3.4.

Yay!!

Question:  Now that we are in the RC phases, only critical bug fixes are allowed?

--
~Ethan~

From victor.stinner at gmail.com  Tue Feb 11 11:16:29 2014
From: victor.stinner at gmail.com (Victor Stinner)
Date: Tue, 11 Feb 2014 11:16:29 +0100
Subject: [python-committers] [Python-Dev] [RELEASED] Python 3.4.0
	release candidate 1
In-Reply-To: <52F9D493.6090100@hastings.org>
References: <52F9D493.6090100@hastings.org>
Message-ID: <CAMpsgwYTGX_cmSk9tVadSW9m97ZXdYERPz8zpXc=go3h9vBPLw@mail.gmail.com>

Hi,

It would be nice to give also the link to the whole changelog in your
emails and on the website:
http://docs.python.org/3.4/whatsnew/changelog.html

Congrats for your RC1 release :-) It's always hard to make developers
stop addings "new minor" changes before the final version :-)

Victor

2014-02-11 8:43 GMT+01:00 Larry Hastings <larry at hastings.org>:
>
> On behalf of the Python development team, I'm delighted to announce
> the first 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 improvements and bug fixes.  Major new features and
> changes in the 3.4 release series include:
>
> * PEP 428, a "pathlib" module providing object-oriented filesystem paths
> * PEP 435, a standardized "enum" module
> * PEP 436, a build enhancement that will help generate introspection
>            information for builtins
> * PEP 442, improved semantics for object finalization
> * PEP 443, adding single-dispatch generic functions to the standard library
> * PEP 445, a new C API for implementing custom memory allocators
> * PEP 446, changing file descriptors to not be inherited by default
>            in subprocesses
> * PEP 450, a new "statistics" module
> * PEP 451, standardizing module metadata for Python's module import system
> * PEP 453, a bundled installer for the *pip* package manager
> * PEP 454, a new "tracemalloc" module for tracing Python memory allocations
> * PEP 456, a new hash algorithm for Python strings and binary data
> * PEP 3154, a new and improved protocol for pickled objects
> * PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O
>
> Python 3.4 is now in "feature freeze", meaning that no new features will be
> added.  The final release is projected for mid-March 2014.
>
>
> To download Python 3.4.0rc1 visit:
>
>     http://www.python.org/download/releases/3.4.0/
>
>
> Please consider trying Python 3.4.0rc1 with your code and reporting any
> new issues you notice to:
>
>      http://bugs.python.org/
>
>
> Enjoy!
>
> --
> Larry Hastings, Release Manager
> larry at hastings.org
> (on behalf of the entire python-dev team and 3.4's contributors)
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com

From rdmurray at bitdance.com  Tue Feb 11 12:42:55 2014
From: rdmurray at bitdance.com (R. David Murray)
Date: Tue, 11 Feb 2014 06:42:55 -0500
Subject: [python-committers] [RELEASED] Python 3.4.0 release candidate 1
In-Reply-To: <52F9E6F2.40907@stoneleaf.us>
References: <52F9D493.6090100@hastings.org> <52F9E6F2.40907@stoneleaf.us>
Message-ID: <20140211114256.408862500C9@webabinitio.net>

On Tue, 11 Feb 2014 01:01:38 -0800, Ethan Furman <ethan at stoneleaf.us> wrote:
> On 02/10/2014 11:43 PM, Larry Hastings wrote:
> >
> > On behalf of the Python development team, I'm delighted to announce
> > the first release candidate of Python 3.4.
> 
> Yay!!
> 
> Question:  Now that we are in the RC phases, only critical bug fixes are allowed?

Only critical fixes go into the next RC, yes (I don't know when Larry
is going to branch 3.4).  Further, every such patch must be reviewed by
at least two committers[*] (which may include the submitter), and signed
off on by the release manager.

Of course, what counts as "critical" sometimes gets debated :)

--David

[*] this is what the "commit review" stage is really for.

From solipsis at pitrou.net  Thu Feb 13 14:15:16 2014
From: solipsis at pitrou.net (Antoine Pitrou)
Date: Thu, 13 Feb 2014 14:15:16 +0100
Subject: [python-committers] RC phase?
Message-ID: <1392297316.2288.0.camel@fsol>


Hello,

So how is the RC phase supposed to work this time? Usually only critical
patches get in, but I see a lot of commits in the last few days.

Regards

Antoine.



From g.brandl at gmx.net  Thu Feb 13 15:46:38 2014
From: g.brandl at gmx.net (Georg Brandl)
Date: Thu, 13 Feb 2014 15:46:38 +0100
Subject: [python-committers] RC phase?
In-Reply-To: <1392297316.2288.0.camel@fsol>
References: <1392297316.2288.0.camel@fsol>
Message-ID: <ldilq8$5ka$1@ger.gmane.org>

Am 13.02.2014 14:15, schrieb Antoine Pitrou:
> 
> Hello,
> 
> So how is the RC phase supposed to work this time? Usually only critical
> patches get in, but I see a lot of commits in the last few days.

For 3.3.0 bugfixing continued on default, and I cherry-picked patches I
considered critical enough into my release repo.  The rest of the
fixes were then merged after final and made their way into 3.3.1.

Larry has a similar plan for 3.4, and I think he will announce it here shortly.

Georg


From zachary.ware+pycommit at gmail.com  Fri Feb 14 18:37:49 2014
From: zachary.ware+pycommit at gmail.com (Zachary Ware)
Date: Fri, 14 Feb 2014 11:37:49 -0600
Subject: [python-committers] RC phase?
In-Reply-To: <ldilq8$5ka$1@ger.gmane.org>
References: <1392297316.2288.0.camel@fsol> <ldilq8$5ka$1@ger.gmane.org>
Message-ID: <CAKJDb-N1WRXsa1QsbJqKgznf_-AFJsi4GgOQOUqQzS2zdfXRZw@mail.gmail.com>

On Thu, Feb 13, 2014 at 8:46 AM, Georg Brandl <g.brandl at gmx.net> wrote:
> Am 13.02.2014 14:15, schrieb Antoine Pitrou:
>>
>> Hello,
>>
>> So how is the RC phase supposed to work this time? Usually only critical
>> patches get in, but I see a lot of commits in the last few days.
>
> For 3.3.0 bugfixing continued on default, and I cherry-picked patches I
> considered critical enough into my release repo.  The rest of the
> fixes were then merged after final and made their way into 3.3.1.
>
> Larry has a similar plan for 3.4, and I think he will announce it here shortly.

That sounds like a good plan to me, and if that's going to be the plan
for the foreseeable future I think the devguide needs bit of an
update.  In particular, with this plan the absolute requirement of
having another core developer review a patch before commit can be
relaxed somewhat, since the RM would be reviewing any post-RC patches
in any case to decide if they should make Final.

Either way, some clarification would be good; I have a couple of
issues that I'd like to commit, but I'm wary of doing so until current
protocol is better defined.

--
Zach

From yselivanov.ml at gmail.com  Thu Feb 20 05:31:30 2014
From: yselivanov.ml at gmail.com (Yury Selivanov)
Date: Wed, 19 Feb 2014 23:31:30 -0500
Subject: [python-committers] new python.org
Message-ID: <53058522.7070401@gmail.com>

Hi,

Do we have a mail list/group where we can discuss the
python.org site?

I've noticed some typos and have some advices, like:

- Python logo has a little yellow 'BETA' label, which may give
some new users impression, that it is the Python Language Beta,
not the python.org website.

- Upcoming events / Latest news aren't updated since 2012

- Freeback Wanted banner should be removed, or at least,
the word "beta" should be dropped.

- etc

Yury

From yselivanov.ml at gmail.com  Thu Feb 20 05:42:52 2014
From: yselivanov.ml at gmail.com (Yury Selivanov)
Date: Wed, 19 Feb 2014 23:42:52 -0500
Subject: [python-committers] new python.org
In-Reply-To: <53058522.7070401@gmail.com>
References: <53058522.7070401@gmail.com>
Message-ID: <530587CC.9020200@gmail.com>


On 2/19/2014, 11:31 PM, Yury Selivanov wrote:
> Hi,
>
> Do we have a mail list/group where we can discuss the
> python.org site?
>
> I've noticed some typos and have some advices, like:
>
> - Python logo has a little yellow 'BETA' label, which may give
> some new users impression, that it is the Python Language Beta,
> not the python.org website.
>
> - Upcoming events / Latest news aren't updated since 2012
>
> - Freeback Wanted banner should be removed, or at least,
> the word "beta" should be dropped.
>
> - etc
>
> Yury
I forgot to add, that I don't want to only criticize,
but to offer some help too.

New python.org is great, and I realize that an insane
amount of work was put into it.

Yury

From richard at python.org  Thu Feb 20 05:45:30 2014
From: richard at python.org (Richard Jones)
Date: Thu, 20 Feb 2014 15:45:30 +1100
Subject: [python-committers] new python.org
In-Reply-To: <530587CC.9020200@gmail.com>
References: <53058522.7070401@gmail.com>
	<530587CC.9020200@gmail.com>
Message-ID: <CAHrZfZC7An0WncQWJp3aTSPdD3CadEDGVny=-2kXVzmWQx3JKQ@mail.gmail.com>

Issues may (should) be reported to the project at
https://github.com/python/pythondotorg


     Richard



On 20 February 2014 15:42, Yury Selivanov <yselivanov.ml at gmail.com> wrote:

>
> On 2/19/2014, 11:31 PM, Yury Selivanov wrote:
>
>> Hi,
>>
>> Do we have a mail list/group where we can discuss the
>> python.org site?
>>
>> I've noticed some typos and have some advices, like:
>>
>> - Python logo has a little yellow 'BETA' label, which may give
>> some new users impression, that it is the Python Language Beta,
>> not the python.org website.
>>
>> - Upcoming events / Latest news aren't updated since 2012
>>
>> - Freeback Wanted banner should be removed, or at least,
>> the word "beta" should be dropped.
>>
>> - etc
>>
>> Yury
>>
> I forgot to add, that I don't want to only criticize,
> but to offer some help too.
>
> New python.org is great, and I realize that an insane
> amount of work was put into it.
>
>
> Yury
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140220/56aabdce/attachment.html>

From michael at voidspace.org.uk  Thu Feb 20 22:06:36 2014
From: michael at voidspace.org.uk (Michael Foord)
Date: Thu, 20 Feb 2014 21:06:36 +0000
Subject: [python-committers] Python Language Summit: please rsvp
Message-ID: <BF6004F7-CC47-4E5E-B757-4D0A63AED9D9@voidspace.org.uk>

Hey all,

The Python Language Summit is on Wednesday 9th April, prior to PyCon in Montreal. The summit will be from 10am to approximately 4pm. If you want to attend you *must* let me know prior to March 15th, as only registered attendees will have food provided for them.

Lunch will be served in room 710 at the Palais at 12:20pm. 

All the best,

Michael Foord

--
http://www.voidspace.org.uk/


May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing 
http://www.sqlite.org/different.html






From benjamin at python.org  Thu Feb 20 22:21:16 2014
From: benjamin at python.org (Benjamin Peterson)
Date: Thu, 20 Feb 2014 13:21:16 -0800
Subject: [python-committers] Python Language Summit: please rsvp
In-Reply-To: <BF6004F7-CC47-4E5E-B757-4D0A63AED9D9@voidspace.org.uk>
References: <BF6004F7-CC47-4E5E-B757-4D0A63AED9D9@voidspace.org.uk>
Message-ID: <1392931276.7223.85876809.7FE81BE6@webmail.messagingengine.com>

I'll have to turn you down. Thanks, though.

On Thu, Feb 20, 2014, at 01:06 PM, Michael Foord wrote:
> Hey all,
> 
> The Python Language Summit is on Wednesday 9th April, prior to PyCon in
> Montreal. The summit will be from 10am to approximately 4pm. If you want
> to attend you *must* let me know prior to March 15th, as only registered
> attendees will have food provided for them.
> 
> Lunch will be served in room 710 at the Palais at 12:20pm. 
> 
> All the best,
> 
> Michael Foord
> 
> --
> http://www.voidspace.org.uk/
> 
> 
> May you do good and not evil
> May you find forgiveness for yourself and forgive others
> May you share freely, never taking more than you give.
> -- the sqlite blessing 
> http://www.sqlite.org/different.html
> 
> 
> 
> 
> 
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers

From georg at python.org  Sun Feb 23 17:25:21 2014
From: georg at python.org (Georg Brandl)
Date: Sun, 23 Feb 2014 17:25:21 +0100
Subject: [python-committers] [RELEASED] Python 3.3.5 release candidate 1
Message-ID: <530A20F1.3030400@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On behalf of the Python development team, I'm happy to announce
the release of Python 3.3.5, release candidate 1.

Python 3.3.5 includes a fix for a regression in zipimport in 3.3.4
(see http://bugs.python.org/issue20621) and a few other bugs.

Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x.  In total, almost 500 API items
are new or improved in Python 3.3.  For a more extensive list of
changes in the 3.3 series, see

    http://docs.python.org/3.3/whatsnew/3.3.html

To download Python 3.3.5 visit:

    http://www.python.org/download/releases/3.3.5/


This is a preview release, please report any bugs to

     http://bugs.python.org/

The final release is scheduled one week from now.


Enjoy!

- -- 
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.3's contributors)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlMKIPEACgkQN9GcIYhpnLCjXACfQwbC/eD/lhKAZ+XCwTwYPVWj
GMwAnjWkbdk7hqsKoh12EiagpGApEPSA
=2BCx
-----END PGP SIGNATURE-----

From larry at hastings.org  Mon Feb 24 05:01:20 2014
From: larry at hastings.org (Larry Hastings)
Date: Sun, 23 Feb 2014 22:01:20 -0600
Subject: [python-committers] [RELEASED] Python 3.4.0 release candidate 2 is
	now available
Message-ID: <530AC410.4020600@hastings.org>



On behalf of the Python development team, I'm delighted to announce
the second 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 improvements and bug fixes.  Major new features and
changes in the 3.4 release series include:

* PEP 428, a "pathlib" module providing object-oriented filesystem paths
* PEP 435, a standardized "enum" module
* PEP 436, a build enhancement that will help generate introspection
            information for builtins
* PEP 442, improved semantics for object finalization
* PEP 443, adding single-dispatch generic functions to the standard library
* PEP 445, a new C API for implementing custom memory allocators
* PEP 446, changing file descriptors to not be inherited by default
            in subprocesses
* PEP 450, a new "statistics" module
* PEP 451, standardizing module metadata for Python's module import system
* PEP 453, a bundled installer for the *pip* package manager
* PEP 454, a new "tracemalloc" module for tracing Python memory allocations
* PEP 456, a new hash algorithm for Python strings and binary data
* PEP 3154, a new and improved protocol for pickled objects
* PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O

Python 3.4 is now in "feature freeze", meaning that no new features will be
added.  The final release is projected for mid-March 2014.


The python.org web site has recently been updated to something 
completely new, and I'm having some difficulty updating it.  For now 
I've made Python 3.4.0rc2 available on the legacy web site:

     http://legacy.python.org/download/releases/3.4.0/

Once I can update the new web site, Python 3.4.0rc2 will be available here:

    http://python.org/download/releases/

(I'm not sure what the final URL will be, but you'll see it listed on 
that page.)


Please consider trying Python 3.4.0rc2 with your code and reporting any
new issues you notice to:

      http://bugs.python.org/


Enjoy!

--
Larry Hastings, Release Manager
larry at hastings.org
(on behalf of the entire python-dev team and 3.4's contributors)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20140223/b4ed849c/attachment.html>