> > I assume your choice for making it a depends instead of a build- > depends was well-founded. A quick check (grep) also shows that > console.py imports epydoc, and uses it. > > My thought is, that maybe upstream should change python-configshell, so > that it no longer needs python-epydoc at runtime, because python- > epydoc is a tool that is apparently intended for build-time use. > Therefore, all python-epydoc processing would be better done at build- > time ? > > Do you think such a change is a possibility ? Or is the use of epydoc > by configshell such that it cannot be easily converted to be done at > build-time ? >
I haven't investigated that yet. My current target for LIO is to get it in good shape and well integrated so that it starts seeing more users. If you have time, you can try knocking off the use of epydoc and see if anything breaks. I am also CCing the upstream devs. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org