Should I write a book on Python Metaprogramming ?

[Alex Martelli]

andrew cooke wrote:

> 
> Alex Martelli said:
> 
>> Paul Rubin wrote:
>>
>>> "andrew cooke" <andrew at acooke.org> writes:
>>>> Personally, I would be interested in something that covered the more
>>>> obscure / newer parts of Python.  I understand that you can generate
>>>> bytecode dyanmically, for example.  Also, what's the difference between
>>>> old + new style classes (including implementation)?  What do the
>>>> various
>>>> special __ methods do etc.
>>>
>>> That belongs in the Python documentation, not in some book you have to
>>> buy separately!!!
>>
>> "That" (each and every one of the items Andrew mentions) IS in the
> 
> whoa.  that's not quite fair.  you're quoting from just the first
> paragraph of my message.  my suggestions for the book included using those

I'm quoting whatever Paul Rubin chose to quote, since it's Paul's
message that I was responding to.  If you think he quoted you "unfairly",
take it up with him (I don't think he did, but, it's between YOU guys).

> facilities to change python to work using protoypes and to provide
> transparent manipulation of objects across the network.  neither of those
> "items" are in the python docs.  i admit that i was too vague in my
> original email, but i was asking for more than already exists in
> documentation.

They aren't in the python docs, I don't think they should be, and
I believe Mr Rubin doesn't think they should be, either -- i.e. that
he was quoting specifically those parts of your request whom he
thinks SHOULD be in the docs (and, I opined in my answer, indeed are).

But I don't think there's anything wrong in wishing for coverage
in a book of stuff that IS covered in the Python docs too -- and
that's the main point of my response, which you chose to cut in
this reply: coverage in a book can differ along many axes from that
in the online docs and therefore provided added value to the reader.


Alex