man/epydoc.1 | 48 24 + 24 - 0 !
man/epydocgui.1 | 8 4 + 4 - 0 !
2 files changed, 28 insertions(+), 28 deletions(-)

 make minor tweaks to manpage syntax.

man/epydocgui.1 | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 mention debian contributions in the manpage.

epydoc/gui.py | 2 0 + 2 - 0 !
1 file changed, 2 deletions(-)

 remove shebang (#!) from .py files to comply with policy.

epydoc/apidoc.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 get rid of string exceptions.
#   One of the changes brought by Python 2.6 is the removal of string
#   exceptions.  A mass bug filing identified Epydoc as having potential
#   problems.  I later spot-checked all of the exceptions in the code, and I
#   believe this is the only one that we have to worry about.
# Bug-Debian: http://bugs.debian.org/585290

epydoc/markup/restructuredtext.py | 24 13 + 11 - 0 !
1 file changed, 13 insertions(+), 11 deletions(-)

 handle problems encountered with docutils 0.6.
#  The problem here is that the child.data element does not always exist any
#  more.  Apparently, the child element is sometimes a string instead.  So, we
#  work around it by only executing the code in question if child.data can be
#  referenced. Thanks to Thomas Hille for research and the initial patch.
# Bug-Debian: http://bugs.debian.org/561793

epydoc/docparser.py | 29 28 + 1 - 0 !
1 file changed, 28 insertions(+), 1 deletion(-)

 fix the tokenizer so comment docstrings work with python 2.6.
# Bug: https://sourceforge.net/tracker/index.php?func=detail&aid=2585292&group_id=32455&atid=405618
# Bug-Debian: http://bugs.debian.org/590112

epydoc/docwriter/latex.py | 2 2 + 0 - 0 !
1 file changed, 2 insertions(+)

 do a better job of handling latex special entities.
#   Mike's original problem was handling special << >> quote characters, i.e.
#   from a French keyboard.  He solved this problem by adding the fontenc
#   package.  In testing, I found that this change caused a HUGE slowdown for
#   PostScript and PDF output, i.e. on the order of several minutes for dvips
#   to render the result.  After digging around on Google, I added the lmodern
#   package and that seems to have solved the problems I observed.
# Bug-Debian: http://bugs.debian.org/614570