[oe] [doc] Standard libs API

[David Farning]

To leverage off of people knowledge of python, I am looking at what
functionality each class makes available.  My concept is that each
classes is a module which: inherits from other class, adds tasks,
exports bitbake methods, and exports python methods.

Attached is a pdf of the section headers for some of the key classes.
(base is incomplete)

I have three questions.

1. What classes would you, as developers, feel are standard classes and
should be covered here?  The classes I have included were just from a
quick look through.

2.  Should I go through and start working on standardizing method
naming?  ie oenote becomes either oe_note(should add class oe to hold
oe_ methods or base_note.(because it is
class base)

3.  Should I add notion of scope by making some methods private.  It
does not appear that there is the capability of defining scope in bb
currently.  I was thinking private methods would have the decorator __
as a prefix.  Private mean not documented
for now.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usermanual.pdf
Type: application/pdf
Size: 89712 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20071108/16bdb5ec/attachment-0002.pdf>