UML and Python

[Terry Hancock]

Does UML work for Python? In particular, given some of the Zope extensions 
to Python:

Interfaces
Components
Acquisitiion
Pluggable Brains

How do you represent them?  And is it useful to you to do so?

I'm not working in a large or small group environment, but alone. So I'm 
mostly interested in its ability to clarify my own code to myself for 
architectural improvement. On the other hand, I do have to communicate with 
others about the design for future use, and I hope to attract other 
developers to the project by being well-designed and well-documented.  And, 
for non-developers, there's also some documentation into the general design 
and capabilities of the software, which might benefit from parts of UML 
(especially interaction, deployment, and use-cases).

Would I be wasting my time to use UML?  And if I do use it, should I 
concentrate on being rigorously correct or just use quick, simplified 
representations?

I'm using "dia" to do this. I created some reverse-engineered drawings 
using happydoc, but I'm actually moving towards just doing new design from 
scratch, because the automatically generated drawing is kind of a pain to 
work with.

I did find this opinion, BTW:
http://www.objectsbydesign.com/projects/python_uml.html
and this collection of UML documents:
http://etna.int-evry.fr/COURS/UML/index.html

Thanks for any opinions or shared experiences,
Terry

-- 
Anansi Spaceworks
http://www.anansispaceworks.com