Michael> Yup. One of the biggest problems I've had with autogenerating
Michael> documentation is that there is usually no way to mark a
Michael> method/function as private other than the double underscore
Michael> name mangling (which isn't usually what you want to do).
Actually, there are two ways:
* single leading underscore => this attribute is private (this is simply
a convention based on the "we're all adults here" rubric)
* double leading underscores without double trailing underscores => the
compiler mangles the name, IMHO mostly to prevent accidental stomping
on attributes in a subclass, not so much to make it truly private
Skip
_______________________________________________
Doc-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/doc-sig
