Name conflict in class hierarchy

[bruno at modulix]

Ralf Muschall wrote:
> Jeffrey Barish wrote:
> 
> [overriding of base class member functions by subclass]
> 
(snip)
> 
> 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.

> or be documented.

s/or/and/


-- 
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in 'onurb at xiludom.gro'.split('@')])"