Miscellaneous design and Python use questions

Travis B. Hartwell travis at travis.aggievilla.org
Fri Feb 18 02:23:41 EST 2000

"Gordon McMillan" <gmcm at hypernet.com> writes:

> You'll probably be happier if you stop thinking in strict OO 
> terms, and realize that Python is all about interfaces, and 
> interfaces are implicit (no need to inherit from some particular 
> base class). To paraphrase Aahz: loosely couple, and 
> componentize the hell out of everything.
   What exactly do you mean by interfaces here?  I think I understand
what your paraphrasing meant:  Don't have your classes / modules /
whatever tied too tightly together (i.e., a good example of
information hiding) and make everything very indepedent.  Is that

> > 2)  I am planning using Python embedded in one of my applications --
> > using C++ Builder for the GUI development and speed-critical
> > portions.  For the rest, I would prefer to use Python just because I
> > have become accustomed to its power.  But, I have been having a few
> > road-blocks in this plan for embedded Python.  I guess I'm having a
> > hard time visualizing exactly where to have the 'dividing line'
> > between C++ and Python and in designing the interfaces between the
> > two.  What are some general hints in designing applications using
> > Python as the engine and C++ as the front-end?
> Write it all in Python first, then decide if you need any C++. I 
> say that as a long time C++/Java/C/.../IBM S370 assembler 
> programmer. Even if you don't use any Python, you'll still save 
> time, because you'll have a model that works.
> - Gordon

More information about the Python-list mailing list