[Pyallegro] Some steps to take over the world

[Grzegorz A. H. <gr...@ti...>]

Looking at the current state of pyallegro I figured out these things
seem missing or are fixable. What do you think about them? I could put
them in a TODO file for future reference.

Mailing list for CVS commit notifications.

Document all C functions and methods with docstrings.

Document all .py functions and methods with docstrings.

Make alpy keys (defines?) work with stable and WIP. Dynamically?

Related to keys, maybe it is possible to detect WIPs at runtime to
enable special methods?

Fix possibly incorrect access of direct memory through
Bitmap_Object_get_data.

Installation documentation for Windows and Linux.

Web page with some info.

More Allegro examples ported to pyallegro.

Standarise on UTF-8 encoding and check all potential functions
passing/returning strings.  exunicode?

Specific examples showing python potential. Or just small games,
to show why Python+Allegro means less lines of code.

New OO Pyallegro?