[Python-Dev] Documenting [C]Python's Internals

[Yaniv Aknin]

>
> This link has all post concatenated together in reverse order of how they
>> should be read. The tags link returns the same page. Does your blog software
>> allow you to make a master post and update with new links as available?
>
>
Ugh, either it doesn't or I couldn't find the feature (I'm using
wordpress.com, if someone has advice, let me know). I can clumsily suggest
scrolling from the end. Also see below about reworking this into a single
multi-chapter document with coherent form.

I would if I were qualified, but I an mot. One way to get people to help
> with details is to publish mistakes. This happens all the time on
> python-list ;-). Pre-review would be nice though.
>

I don't mind so much the 'humiliation' of published mistakes, but since I
want this to be perceived as reference grade material, I prefer pre-review.
Yesterday my first mistake was found (ugh), I published an 'Errata Policy'
and will stick to it from now on (see the blog itself for details of the
mistake). Thankfully, I've been approached already about pre-review, we'll
see how this develops (this doesn't mean other people can't also offer
themselves, six eyeballs are better than four).

People have asked for an internals-doc since I started over a decade ago. A
> coherent CPython3.2 Internals would be nice to have with the 3.2 release
> next December or so, whether or not it was made 'official'.
>

I'm targeting py3k anyway, and while I expect a bug lull in my writing
between early June and early September, I think December is a realistic date
for me to have good coverage CPython 3.2's core and rework the content into
a more reference-material-ish form. That said, working things into
reference-material form could be significant work, so if python-dev doesn't
show interest in this I think the blog posts are good enough. Other people,
this is your queue to chime in and state your opinion about this appearing
on python.org somewhere.

Cheers!
 - Yaniv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100521/8a5a049a/attachment.html>