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 yselivanov
Recipients Claudiu.Popa, berker.peksag, bignose, eric.araujo, martin.panter, matrixise, r.david.murray, rhettinger, yselivanov
Date 2014-04-15.20:09:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397592565.09.0.10107850638.issue12916@psf.upfronthosting.co.za>
In-reply-to
Content
David:

> The precedent has already been set by the 'cleandoc' function, I think.  This one seems to go right along with that one.

What do you think if we keep the function in pydoc module, but document it and make it public?  I agree, that there is a precedent of having non-introspection APIs in inspect, but I'd still like to keep it minimal.  Having this function in pydoc also makes sense, as it's more about python docstring convention, than introspection (cleandoc() is used by getdoc(), which is why it is in inspect after all)
History
Date User Action Args
2014-04-15 20:09:25yselivanovsetrecipients: + yselivanov, rhettinger, eric.araujo, r.david.murray, Claudiu.Popa, bignose, berker.peksag, martin.panter, matrixise
2014-04-15 20:09:25yselivanovsetmessageid: <1397592565.09.0.10107850638.issue12916@psf.upfronthosting.co.za>
2014-04-15 20:09:25yselivanovlinkissue12916 messages
2014-04-15 20:09:24yselivanovcreate