How to convert (unicode) text to image?

Nobody nobody at nowhere.com
Mon Aug 30 21:09:30 CEST 2010


On Mon, 30 Aug 2010 12:50:32 +0200, Thomas Jollans wrote:

>> Face the facts dude.  The Python docs have some major problems.
>> They were pretty good when Python was a new, cool, project used
>> by a handful of geeks.  They are good relative to the "average"
>> (whatever that is) open source project -- but that bar is so low
>> as to be a string lying on the ground.
> 
> Actually, the Python standard library reference manual is excellent. At
> least that's my opinion.

The core library documentation isn't as bad as most Python documentation,
but it's still far from adequate for core language functionality.

Anyone who thinks that the library documentation is "good" has become too
accustomed to FOSS "documentation" which is little more than an HTMLified
copy of the header files, with each function's documentation consisting of
a prototype and a one-sentence description which provides no information
which couldn't have been guessed from the function name.

For add-ons, you can get away with second-rate documentation. If the
documentation isn't sufficient to allow the module to be used, don't
use it; write your own instead. But that doesn't work for core language
features.




More information about the Python-list mailing list