On 3/28/2010 9:46 AM, Ethan Furman wrote:
Robert Kern wrote:
On 2010-03-27 08:19 , Ethan Furman wrote:
Okay, different post for my actual questions. :)
On the PyPI page for strait (http://pypi.python.org/pypi/strait/0.5.1)
it has the example of choosing which methods to keep in the composed
c
On 2010-03-28 08:46 , Ethan Furman wrote:
Robert Kern wrote:
On 2010-03-27 08:19 , Ethan Furman wrote:
Okay, different post for my actual questions. :)
On the PyPI page for strait (http://pypi.python.org/pypi/strait/0.5.1)
it has the example of choosing which methods to keep in the composed
c
Robert Kern wrote:
On 2010-03-27 08:19 , Ethan Furman wrote:
Okay, different post for my actual questions. :)
On the PyPI page for strait (http://pypi.python.org/pypi/strait/0.5.1)
it has the example of choosing which methods to keep in the composed
class:
class TOSWidget(BaseWidget):
__me
On 2010-03-27 08:19 , Ethan Furman wrote:
Okay, different post for my actual questions. :)
On the PyPI page for strait (http://pypi.python.org/pypi/strait/0.5.1)
it has the example of choosing which methods to keep in the composed class:
class TOSWidget(BaseWidget):
__metaclass__ = include(Pac
Wow.
I just stumbled across one of Michele Simionato's offerings, called
simple traits (strait for short) which looks *really* cool.
You can find it here: http://pypi.python.org/pypi/strait/0.5.1
Extremely quick summary:
Instead of multiple inheritance, with it's range of pro
Okay, different post for my actual questions. :)
On the PyPI page for strait (http://pypi.python.org/pypi/strait/0.5.1)
it has the example of choosing which methods to keep in the composed class:
class TOSWidget(BaseWidget):
__metaclass__ = include(Pack, Place, Grid)
info = Pack.info.
