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 eric.snow
Recipients Claudiu.Popa, berker.peksag, bignose, eric.araujo, eric.snow, martin.panter, matrixise, r.david.murray, rhettinger, yselivanov
Date 2014-04-16.14:11:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree with Éric that exposing splidoc publicly in the inspect module is the right thing.  inspect already has other similar functions.  If it doesn't land in inspect then the only other place that makes real sense to me would be a new module (docstring?).  However, that seems like overkill to me.

Furthermore, pydoc doesn't seem like a good place to expose the function (or perhaps any function <wink>).  It isn't a module relating explicitly to docstrings so much as to exposing API documentation.  The use of splitdoc there is an implementation detail while splitdoc itself is generally useful.  That said, I would still expect splitdoc to be exposed in pydoc for backward compatibility (via "from inspect import splitdoc").
Date User Action Args
2014-04-16 14:11:08eric.snowsetrecipients: + eric.snow, rhettinger, eric.araujo, r.david.murray, Claudiu.Popa, bignose, berker.peksag, martin.panter, yselivanov, matrixise
2014-04-16 14:11:08eric.snowsetmessageid: <>
2014-04-16 14:11:07eric.snowlinkissue12916 messages
2014-04-16 14:11:07eric.snowcreate