En Wed, 04 Feb 2009 21:12:58 -0200, andrew cooke
escribió:
On Feb 4, 7:49 pm, andrew cooke wrote:
This leads to a circular dependency - the base class wants to import
the components, which in turn want to import the base class.
well, to partially answer my own question, this is certainly
po
On Feb 4, 7:49 pm, andrew cooke wrote:
> This leads to a circular dependency - the base class wants to import
> the components, which in turn want to import the base class.
>
> Is there any standard solution to this?
well, to partially answer my own question, this is certainly
possible. in the g
Is there a good solution to the following problem?
I have a library whose components I would like to separate into
distinct modules. These components inherit from a common base class
that provides common functionality (the inheritance is important only
for implementation; there's a separate ABC m
