Since parts of the python standard library can dramatically change every x.x release. I found learning to apply and maintain code written in the "standard library" to be cyclical hell in a hand basket. Much of the documentation these days is along the lines of:
No, usage of this or that feature was deprecated. No, though not documented, it's done this way now. No your getting this error because.. well.. we don't know, its ether 2.5, 2.6, or 3.0, figure it out.
Given this experience, I don't see how a dead tree covering a particular one is of all that much value. To me a selling proposition would be one which provides a continuity in documentation with fully explained use-cases of features after 2.5- for those of us who have had to pick up the language and deal with the mess of non-versioned code. A mess that whether the authors of the language like it or not, do have a hand in being responsible for.
