looking at upstream code here https://sourceforge.net/p/epydoc/code/HEAD/tree/trunk/epydoc/src/epydoc/cli.py#l507 it uses print without parenthesis
Code is extremally old (python 2.4) and looks like not updated for years. Just fix of printing will be waste of time: 1. stdlib changes (import __builtin__, exceptions, popen2,cStringIO|StringIO,thread,Tkinter,tkFileDialog), 2. exceptions (old raise syntax, except Exception, value) 3. print function 4. long type usage 5. manual backports for python 2.2 present 6. sys.stderr write string (for py3 bytes is required) 7. backquotes (`num_lines+1`) 8. exec pysrc in globals(), localdict
Last code change in 2009 - more, than 10 years ago - looks like abandoned
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=55b2187afee5a25e52b1fde09a8f8e1e3d2db545 commit 55b2187afee5a25e52b1fde09a8f8e1e3d2db545 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-01-29 07:16:25 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-01-29 07:23:23 +0000 package.mask: Last rite dev-python/epydoc Bug: https://bugs.gentoo.org/706218 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 5 +++++ 1 file changed, 5 insertions(+)
Should we fork and fix this dead code?
