On 10/03/2012 01:54 PM, Larry Hastings wrote: > > On 10/03/2012 01:45 PM, Skip Montanaro wrote: >> 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? > > Here's a short list of proposed changes for 3.4--basically all the stuff that > didn't make it in to 3.3: > > Candidate PEPs: > > * PEP 395: Qualified Names for Modules > * PEP 3143: Standard daemon process library > * PEP 3154: Pickle protocol version 4 > > Other proposed large-scale changes: > > * Breaking out standard library and docs in separate repos > * Addition of the "packaging" module, deprecating "distutils" > * Addition of the "regex" module > * Email version 6 > * A standard event-loop interface (PEP by Jim Fulton pending) > > > 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. > > The schedule proposes six weeks between feature-freeze and release. Looks more like 3 months, which is fine. Georg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4