Your message dated Wed, 31 Jul 2019 21:22:26 -0500
with message-id
<CAL5KwF-_Zi2=s9ruzsjnc+epxnmwv24fdfhyrlzy5cqtd3g...@mail.gmail.com>
and subject line Resolved along with 932585
has caused the Debian Bug report #881560,
regarding pywbem: Please migrate away from Epydoc if possible
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
881560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881560
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pywbem
Severity: wishlist
Hi,
If possible, please consider moving away from the use of Epydoc in your
package. Epydoc is basically unmaintained upstream. Also, it is only
supported for Python 2, so it will reach its end of life along with
Python 2 sometime in 2020.
I will continue to maintain the Epydoc packages in Debian as long as I
can, acting as de facto upstream. However, once Python 2 is unsupported
in Debian, I'm not sure that we'll have too many options to keep it
alive. Migrating it to Python 3 is a fairly large job that I don't
have the time or the expertise to take on right now.
For my own Python code, I have recently converted to Sphinx using the
Napolean plugin. At [1], I can offer you (or your upstream) a hack-ish
script to convert common Epydoc markup to Google-style docstrings. It's
not perfect, but it would get you much of the way toward working code.
Thanks,
Ken (maintainer for python-epydoc)
[1]
https://bitbucket.org/cedarsolutions/cedar-backup3/src/73037a2/util/sphinx-convert
--- End Message ---
--- Begin Message ---
This bug was resolved along with the NMU that fixed #932585. Epydoc
is no longer needed. It does not appear to be necessary.
KEN
--
Kenneth J. Pronovici <[email protected]>
--- End Message ---
