Python Documentation Blows!

[Michael]

> The trick with wxPython and wxWindows docs is that the entirety of 
> wxWindows is available to wxPython, through (on the most part) 
> identical class and function calls.  In those cases when there are 
> differences, the differences are noted.
>
> For those who need more documentation, usually, example code is as 
> good documentation as you'd find.  For that, there is the wxPython demo.
>
> In general, Robin Dunn is the only person who is maintaining wxPython, 
> and I am glad that he's spending his time with wxPython, rather than 
> the documentation.
>
> If you are having problems understanding the wxWidgets documentation, 
> learning a bit of C (not much, just a bit) will likely go a /long/ way 
> towards understanding the calling conventions.

Very true, but wxPython still is horribly documented. Documentation of 
the C version of something is really not very friendly especially to new 
Python programmers. I for one would be glad to buy a book about wxPython 
if someone a lot more experienced than myself cared to write such a 
book. I do know C but I still find working from the wxWindows docs 
frustrating with a lot of trial and error required.