iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Some PEP status updates based on my current priorities

This commit is contained in:
Nick Coghlan 2014-09-23 19:44:33 +10:00
parent cfb0a47ed5
commit 2c84a77cfc
3 changed files with 17 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
pep-0432.txt
View File

@ -3,7 +3,7 @@ Title: Simplifying the CPython startup sequence
Version: $Revision$
Last-Modified: $Date$
Author: Nick Coghlan <ncoghlan@gmail.com>
Status: Deferred
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
Created: 28-Dec-2012
@ -25,31 +25,6 @@ resolution for most of these should become clearer as the reference
implementation is developed.
PEP Deferral
============
Python 3.4 is nearing its first alpha, and already includes a couple of
significant low level changes in PEP 445 (memory allocator customisation)
and PEP 442 (safe object finalization). As a result of the latter PEP,
the shutdown procedure of CPython has also been changed to be more heavily
reliant on the cyclic garbage collector, significantly reducing the
number of modules that will experience the "module globals set to None"
behaviour that is used to deliberate break cycles and attempt to releases
more external resources cleanly.
Furthermore, I am heavily involved in the current round of updates to the
Python packaging ecosystem (as both the lead author of PEP 426 and
BDFL-delegate for several other PEPs), leaving little to spare to work on
this proposal. The other developers I would trust to lead this effort are
also working on other things.
So, due to those practical resource constraints, the proximity of Python
3.4 deadlines, and recognition that making too many significant changes to
the low level CPython infrastructure in one release is likely to be unwise,
further work on this PEP has been deferred to the Python 3.5 development
cycle.
Proposal
========

9
pep-0462.txt
View File

@ -3,7 +3,7 @@ Title: Core development workflow automation for CPython
Version: $Revision$
Last-Modified: $Date$
Author: Nick Coghlan <ncoghlan@gmail.com>
Status: Draft
Status: Deferred
Type: Process
Content-Type: text/x-rst
Created: 23-Jan-2014
@ -22,6 +22,13 @@ experience for other contributors that are reliant on the core team to get
their changes incorporated.
PEP Deferral
============
This PEP is deferred largely because I don't currently have time to work on
it. If anyone would like to take it over, let me know.
Rationale for changes to the core development workflow
======================================================

9
pep-0474.txt
View File

@ -3,7 +3,7 @@ Title: Creating forge.python.org
Version: $Revision$
Last-Modified: $Date$
Author: Nick Coghlan <ncoghlan@gmail.com>
Status: Draft
Status: Deferred
Type: Process
Content-Type: text/x-rst
Created: 19-Jul-2014
@ -23,6 +23,13 @@ This PEP does *not* propose any changes to the core development workflow
for CPython itself (see PEP 462 in relation to that).
PEP Deferral
============
This PEP is deferred largely because I don't currently have time to work on
it. If anyone would like to take it over, let me know.
Proposal
========