This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xtreak
Recipients christian.heimes, docs@python, steve.dower, xtreak
Date 2019-06-24.19:08:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561403284.84.0.368020061971.issue37390@roundup.psfhosted.org>
In-reply-to
Content
I think my approach suffers from the drawback where duplicate items cannot be separated correctly as you have mentioned. Example as below where socket.connect and socket.connect_ex emit same event and I am not able to retrieve the function at which the audit event block is present thus generating the same entry twice in the table. Maybe I need to store some more metadata.

1153:.. method:: socket.connect(address)
1165:   .. audit-event:: socket.connect "self address"
1174:.. method:: socket.connect_ex(address)
1183:   .. audit-event:: socket.connect "self address"

> * include links back to the section where they came from

Sphinx doesn't seem to support hyperlinking to line numbers. One approach would be to just link to the functions that emit the events that could solve the above problem too.

I did this as a PoC and kind of stuck with moving the file to a separate to a different table of content. I also seemed to have hit a sphinx bug that I couldn't get out of and my skills are limited too in Sphinx. I will give it another try over this week to see if I can come up with something mergeable :)
History
Date User Action Args
2019-06-24 19:08:04xtreaksetrecipients: + xtreak, christian.heimes, docs@python, steve.dower
2019-06-24 19:08:04xtreaksetmessageid: <1561403284.84.0.368020061971.issue37390@roundup.psfhosted.org>
2019-06-24 19:08:04xtreaklinkissue37390 messages
2019-06-24 19:08:04xtreakcreate