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 berker.peksag
Recipients Claudiu.Popa, berker.peksag, bignose, eric.araujo, eric.snow, martin.panter, matrixise, r.david.murray, rhettinger, serhiy.storchaka, yselivanov
Date 2015-03-09.07:31:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425886305.96.0.682868520614.issue12916@psf.upfronthosting.co.za>
In-reply-to
Content
pydoc doesn't have public API other than its CLI and the help() function. I'd cleanup or even rewrite pydoc before declare anything public in it. On the other hand, there are already functions related to splitdoc() in the inspect module: https://docs.python.org/3/library/inspect.html#retrieving-source-code See also issue 18956.

There is no rush to make splitdoc() public. We can improve pydoc in 3.5 and 3.6 timeline and then decide what's should be part of the public API.
History
Date User Action Args
2015-03-09 07:31:46berker.peksagsetrecipients: + berker.peksag, rhettinger, eric.araujo, r.david.murray, Claudiu.Popa, bignose, eric.snow, martin.panter, serhiy.storchaka, yselivanov, matrixise
2015-03-09 07:31:45berker.peksagsetmessageid: <1425886305.96.0.682868520614.issue12916@psf.upfronthosting.co.za>
2015-03-09 07:31:45berker.peksaglinkissue12916 messages
2015-03-09 07:31:45berker.peksagcreate