On Sun, 6 Jan 2013 08:25:44 +0100 (CET) nick.coghlan python-checkins@python.org wrote:
http://hg.python.org/peps/rev/3eb7e4b587da changeset: 4654:3eb7e4b587da user: Nick Coghlan ncoghlan@gmail.com date: Sun Jan 06 17:22:45 2013 +1000 summary: Updates in response to Barry Warsaw's feedback
files: pep-0432.txt | 217 ++++++++++++++++++++++++++------------ 1 files changed, 146 insertions(+), 71 deletions(-)
diff --git a/pep-0432.txt b/pep-0432.txt --- a/pep-0432.txt +++ b/pep-0432.txt @@ -40,19 +40,21 @@ well-defined phases during the startup sequence:
- Pre-Initialization - no interpreter available
-* Initialization - interpreter partially available -* Initialized - full interpreter available, __main__ related metadata +* Initializing - interpreter partially available +* Initialized - interpreter available, __main__ related metadata incomplete -* Main Execution - optional state, __main__ related metadata populated,
- bytecode executing in the __main__ module namespace
+* Main Execution - __main__ related metadata populated, bytecode
- executing in the __main__ module namespace (embedding applications
- may choose not to use this phase)
Since we are here, I would bikeshed a little and point out that "initializing" and "initialiazed" are states, not phases. Either way, the nomenclature should be consistent.
Regards
Antoine.
On Sun, Jan 6, 2013 at 10:26 PM, Antoine Pitrou solipsis@pitrou.net wrote:
Since we are here, I would bikeshed a little and point out that "initializing" and "initialiazed" are states, not phases. Either way, the nomenclature should be consistent.
States and phases are generally the same thing (e.g. states of matter vs phases of matter).
I've switched back and forth between state, stage and phase at various times, though, so the PEP is currently internally inconsistent. If there are any leftover "state" and "stage" references, it's just a mistake since "phase" is the terminology I finally settled on.
Cheers, Nick.