Name conflict in class hierarchy
rmuschall at tecont.de
Tue May 23 09:04:52 CEST 2006
bruno at modulix wrote:
>> In Python, a function not intended to be overriden should be either
>> have a name starting with an underscore
> actually with *two* underscores. The single-leading-underscore naming
> scheme is the convention for 'protected' (read: 'implementation, not
> API') attributes.
That's what I meant. "A.func" looked like an internal implementation
>> or be documented.
Having the implementation details documented too would be nice, but
hardly enforceable in real life.
More information about the Python-list