On 5 March 2010 12:31, Kevin Horn firstname.lastname@example.org wrote:
On Thu, Mar 4, 2010 at 5:05 PM, email@example.com wrote:
On 10:49 pm, firstname.lastname@example.org wrote:
If you look up a class, like "twisted.internet.defer.Deferred" for example, the link looks like this:
Pretty simple right? But if you look up a function or method like "twisted.internet.defer.Deferred.callback", the link has an anchor, like so:
So we'll need to do some checking on either the api docs or on twisted itself to determine what sort of object is being linked to. Shouldn't be super-difficult, just haven't had time yet.
Did you notice that
http://twistedmatrix.com/documents/9.0.0/api/twisted.internet.defer.Deferred... also exists?
I hadn't actually. If all functions and methods have a similar page in the PyDoctor output, then I think what I have now will pretty much work as-is (almost). Do we think that just generating links to the individual function/method pages is acceptable?
It's what the lore-processed documentation currently links to. It would be nice to fix this (and I sort of vaguely know how), but that should in no way hold up the move away from lore!