On 2:59 PM, Chris Rebert wrote:
On Thu, Oct 28, 2010 at 8:33 PM, Baskaran Sankaran wrote:
Sorry for the confusion; fooz(), track() and barz() are all members of their
respective classes. I must have missed the self argument while creating the
synthetic example.
Yeah, I realize the mutual impor
On Thu, Oct 28, 2010 at 8:33 PM, Baskaran Sankaran wrote:
> Sorry for the confusion; fooz(), track() and barz() are all members of their
> respective classes. I must have missed the self argument while creating the
> synthetic example.
>
> Yeah, I realize the mutual import is a bad idea. So, if I
Sorry for the confusion; fooz(), track() and barz() are all members of their
respective classes. I must have missed the self argument while creating the
synthetic example.
Yeah, I realize the mutual import is a bad idea. So, if I merge them into a
single module (but still retaining the two classes
On 2:59 PM, Baskaran Sankaran wrote:
Hi,
I have two classes in separate python modules and I need to access some
methods of the either classes from the other. They are not in base and
derived class relationship.
Please see the example below. Foo imports Bar and inside the Foo class it
creates a
Hi,
I have two classes in separate python modules and I need to access some
methods of the either classes from the other. They are not in base and
derived class relationship.
Please see the example below. Foo imports Bar and inside the Foo class it
creates a Bar obj and then calls Bar.barz(). Now
