[Twisted-Python] documentation / kqueue / feedback
nitro at dr-code.org
Thu Apr 17 04:41:01 EDT 2008
Am 17.04.2008, 08:49 Uhr, schrieb Gabriel Rossetti
<mailing_lists at evotex.ch>:
> there are links that are always broken, like for example :
> if you look at this line :
> "If you only need the final exit code (like
> |commands.getstatusoutput(cmd)|), the
> function is useful."
> The link being :
> All those types of links in the howtos/tutorials are bad. Should I write
> a bugreport? If so, would an explanation like the one above suffice (I
> can't find all the links in the tutorials that are bad)?
Couldn't "find broken links" be automated in some way? Whenever the docs
are build there would be a simple python script extracting all hrefs out
of the generated html document then. Then it would try to access each one
of them and write the failed ones inluding the document they appeared in
into a log file or something?
More information about the Twisted-Python