[Python-ideas] PEP 432: Simplifying the CPython startup sequence
Mark Shannon
mark at hotpy.org
Fri Dec 28 16:45:47 CET 2012
More information about the Python-ideas mailing list
Fri Dec 28 16:45:47 CET 2012
- Previous message: [Python-ideas] PEP 432: Simplifying the CPython startup sequence
- Next message: [Python-ideas] PEP 432: Simplifying the CPython startup sequence
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 27/12/12 15:10, Nick Coghlan wrote: Hi, > This PEP proposes that CPython move to an explicit 2-phase initialisation Why only two phases? I was thinking about the initialisation sequence a while ago and thought that a three or four phase sequence might be appropriate. What matters is that the state in between phases is well defined and simple to understand. You might want to take a look at rubinius which implements most of its core components in Ruby, so needs a clearly defined startup sequence. http://rubini.us/doc/en/bootstrapping/ (Rubinius using 7 phases, but that would be overkill for CPython) Cheers, Mark.
- Previous message: [Python-ideas] PEP 432: Simplifying the CPython startup sequence
- Next message: [Python-ideas] PEP 432: Simplifying the CPython startup sequence
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list