Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-04 Thread Christoph Burgmer
Am Sonntag, 3. Februar 2008 schrieb Kenneth Pronovici: 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. Just upgraded from

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-03 Thread Christoph Burgmer
Am Sonntag, 3. Februar 2008 schrieb Edward Loper: If a package is available globally to the system in addition to the version in the local directory epydoc seems to prefer the global file over the local in some occasions when building the package's API. What command line arguments are you

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-03 Thread Edward Loper
Try specifying the modules using filenames. I.e., add either .py (if they're modules) or a trailing / (if they're directories) to the following line: modules: cjknife buildcjkdb cjklib and see if that makes it do the right thing. Thanks, -Edward -- To UNSUBSCRIBE, email to [EMAIL

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-03 Thread Christoph Burgmer
Am Sonntag, 3. Februar 2008 schrieb Edward Loper: Try specifying the modules using filenames. I.e., add either .py (if they're modules) or a trailing / (if they're directories) to the following line: modules: cjknife buildcjkdb cjklib and see if that makes it do the right thing. modules:

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-03 Thread Edward Loper
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

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-03 Thread Kenneth Pronovici
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.

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-02 Thread Christoph Burgmer
Package: python-epydoc Version: 3.0~beta1-5 Severity: normal If a package is available globally to the system in addition to the version in the local directory epydoc seems to prefer the global file over the local in some occasions when building the package's API. I am working with some files on

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-02 Thread Kenneth Pronovici
On Feb 2, 2008 2:01 PM, Christoph Burgmer [EMAIL PROTECTED] wrote: Package: python-epydoc Version: 3.0~beta1-5 Severity: normal If a package is available globally to the system in addition to the version in the local directory epydoc seems to prefer the global file over the local in some

Bug#463734: python-epydoc: epydoc parses file in global path instead of local directory

2008-02-02 Thread Edward Loper
If a package is available globally to the system in addition to the version in the local directory epydoc seems to prefer the global file over the local in some occasions when building the package's API. What command line arguments are you using, and what directory are you executing it from?