Although this is not what you are asking but I'm wondering why you need to read CPython implementation. I have been using Python for 7 or 8 years but I've never encountered any situations where I need to read CPython implementation. I needed to read library implementations and installer codes, though.
CPython worked great for me. I don't want to read a large piece of software, like CPython, unless it is really really necessary. I'm curious. Aki- On Dec 29, 5:22 pm, thmpsn....@gmail.com wrote: > I've just downloaded Python's mainstream implementation (CPython), > which is written in C. Not to my surprise, I feel like I'm looking at > unstructured spaghetti, and I'm having trouble figuring out how it all > works together. (Please bear with me; I'm just going through the usual > frustration that anyone goes through when trying to see the > organization of a C program :) > > So, I have two queries: > > 1. Can anyone explain to me what kind of program structuring technique > (which paradigm, etc) CPython uses? How do modules interact together? > What conventions does it use? > > 2. Have there been any suggestions in the past to rewrite Python's > mainstream implementation in C++ (or why wasn't it done this way from > the beginning)? -- http://mail.python.org/mailman/listinfo/python-list
