<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
On 10/03/2012 01:45 PM, Skip Montanaro wrote:<br>
</div>
<blockquote
cite="mid:CANc-5UzRzVi-ntCGj6vnchLp-1gTHq_igQTycD6-3ir0-F2qiA@mail.gmail.com"
type="cite">
Is there a rough list of changes for 3.4 written down somewhere,
or is
that only to be inferred based on PEPs whose Python-Version header
reads "3.4"? How confident are you that the schedule you've
proposed
gives enough time for proposed changes to be implemented and to
stablize?
</blockquote>
<br>
Here's a short list of proposed changes for 3.4--basically all the
stuff that didn't make it in to 3.3:<br>
<blockquote>Candidate PEPs:<br>
<br>
* PEP 395: Qualified Names for Modules<br>
* PEP 3143: Standard daemon process library<br>
* PEP 3154: Pickle protocol version 4<br>
<br>
Other proposed large-scale changes:<br>
<br>
* Breaking out standard library and docs in separate repos<br>
* Addition of the "packaging" module, deprecating "distutils"<br>
* Addition of the "regex" module<br>
* Email version 6<br>
* A standard event-loop interface (PEP by Jim Fulton pending)<br>
</blockquote>
<br>
As for the rest of it, my understanding was that there is no longer
any great plan written in the stars for Python releases. Python
releases are comprised of whatever features people propose,
implement, and are willing to support, that they can get done in
time for the beta cutoff. From that perspective, the schedule
drives the features more than the other-way around.<br>
<br>
The schedule proposes six weeks between feature-freeze and release.
If that isn't enough we'll slip a little. But given that we have
little idea what features will make it in to 3.4, it's hard to say
for certain whether or not that's enough time. At this point all I
can do is propose a schedule and hope for the best.<br>
<br>
Here's hoping,<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>