The bug that you attached (stacktrace.txt & codeproducingexception.txt) should be fixed in the epydoc 3.0 stable release (which was released just a few days ago, and hasn't made its way to a debian package yet.
I'll look into why epydoc might pick up the wrong versions of modules when you specify them as python names (foo or foo.bar) rather than paths (foo.py or foo/bar/). -Edward -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
