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 a local copy which are also installed as a
packaged version in an older version.

File AAA is installed under /usr/bin/AAA through the package and file BBB is
installed under /usr/lib/python2.4/site-packages/*/BBB.

Changes in files AAA and BBB do only show up for the latter file BBB in the
generated API. The content for AAA seems to be taken from the older version
under /usr/bin/AAA whereas BBBs newer version from the local copy is read.

As I'm not quite sure whether or not it's a upstream problem I rather submit
a report here.

Thanks,

Christoph

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22 (PREEMPT)
Locale: [EMAIL PROTECTED], LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-epydoc depends on:
ii  python                        2.4.4-6    An interactive high-level object-o
ii  python-support                0.7.6      automated rebuilding support for p

Versions of packages python-epydoc recommends:
ii  ghostscript [gs-common]    8.61.dfsg.1-1 The GPL Ghostscript PostScript/PDF
ii  graphviz                   2.16-3        rich set of graph drawing tools
ii  gs-common                  8.61.dfsg.1-1 Transitional package
ii  python-docutils            0.4-5         Utilities for the documentation of
pn  python-tk                  <none>        (no description available)
ii  texlive-fonts-recommended  2007-13       TeX Live: Recommended fonts
ii  texlive-latex-base         2007-13       TeX Live: Basic LaTeX packages
pn  texlive-latex-extra        <none>        (no description available)
ii  texlive-latex-recommended  2007-13       TeX Live: LaTeX recommended packag

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to