| 2010-02-06 04:36:23 |
Michael Hudson-Doyle |
description |
Originally reported as Twisted issue 1886:
> This has two bad effects:
> it's hard for packagers to package pydoctor's output for the different bits of twisted because if (say) twisted web's docs are in /usr/share/doc/twisted-web/ they should like to twisted core's docs in /usr/share/doc/twisted-core/ and this isn't currently possible.
> similarly, the pydoctor output for nevow should link to the pydoctor output for twisted, if it knows where it is.
> I think this can be addressed by loading a bunch of systems that know the base url of their documentation, and having the documentation generator look in more than just the system being generated when trying to link to something.
> Having written all this out, I don't think it should be too hard... |
Originally reported as Twisted issue 1886.
This has two bad effects:
it's hard for packagers to package pydoctor's output for the different bits of twisted because if (say) twisted web's docs are in /usr/share/doc/twisted-web/ they should link to twisted core's docs in /usr/share/doc/twisted-core/ and this isn't currently possible.
Similarly, the pydoctor output for nevow should link to the pydoctor output for twisted, if it knows where it is.
I think this can be addressed by loading a bunch of systems that know the base url of their documentation, and having the documentation generator look in more than just the system being generated when trying to link to something.
Having written all this out, I don't think it should be too hard...
|
|
