Christoph - I'll hopefully get 3.0 uploaded later today or tomorrow. After it hits the archive, please re-test the stacktrace.txt scenario. If the new version doesn't fix that problem, please file a separate bug.
Edward - I'll leave this bug open while you're looking into wrong-versions issue. Let me know if you want me to file a separate SF bug report. KEN On Feb 3, 2008 12:01 PM, Edward Loper <[EMAIL PROTECTED]> wrote: > 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 > > -- Kenneth J. Pronovici <[EMAIL PROTECTED]> http://www.cedar-solutions.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
