[Python-checkins] peps: Proofread before posting to python-ideas

nick.coghlan python-checkins at python.org
Thu Dec 27 16:10:16 CET 2012


http://hg.python.org/peps/rev/91befe5c72fd
changeset:   4637:91befe5c72fd
user:        Nick Coghlan <ncoghlan at gmail.com>
date:        Fri Dec 28 01:10:05 2012 +1000
summary:
  Proofread before posting to python-ideas

files:
  pep-0432.txt |  28 +++++++++++++++++-----------
  1 files changed, 17 insertions(+), 11 deletions(-)


diff --git a/pep-0432.txt b/pep-0432.txt
--- a/pep-0432.txt
+++ b/pep-0432.txt
@@ -238,11 +238,12 @@
 status quo).
 
 In addition, the current thread will possess a valid Python thread state,
-allow any further configuration data to be stored.
+allow any further configuration data to be stored on the interpreter object
+rather than in C process globals.
 
-Any call to Py_InitStart() must have a matching call to Py_Finalize(). It
-is acceptable to skip calling Py_InitFinish() in between (e.g. if
-attempting to read the configuration settings fails)
+Any call to Py_BeginInitialization() must have a matching call to
+Py_Finalize(). It is acceptable to skip calling Py_EndInitialization() in
+between (e.g. if attempting to read the configuration settings fails)
 
 
 Determining the remaining configuration settings
@@ -343,6 +344,11 @@
 initialisation. As the PEP matures, these will be discussed in more detail
 on a case by case basis.
 
+The Py_Initialize() style of initialisation will continue to be supported. It
+will use the new API internally, but will continue to exhibit the same
+behaviour as it does today, ensuring that sys.argv is not set until a
+subsequent PySys_SetArgv call.
+
 
 A System Python Executable
 ==========================
@@ -364,14 +370,14 @@
 
 One final aspect not addressed by the general embedding changes above is
 the current inaccessibility of the core logic for deciding between the
-different execution modes supported by CPython::
+different execution modes supported by CPython:
 
-    * script execution
-    * directory/zipfile execution
-    * command execution ("-c" switch)
-    * module or package execution ("-m" switch)
-    * execution from stdin (non-interactive)
-    * interactive stdin
+* script execution
+* directory/zipfile execution
+* command execution ("-c" switch)
+* module or package execution ("-m" switch)
+* execution from stdin (non-interactive)
+* interactive stdin
 
 <TBD: concrete proposal for better exposing the __main__ execution step>
 

-- 
Repository URL: http://hg.python.org/peps


More information about the Python-checkins mailing list