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 eric.snow, ncoghlan
Date 2013-08-02.04:53:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375419191.08.0.571987948186.issue18626@psf.upfronthosting.co.za>
In-reply-to
Content
At the risk of unnecessary complication, there is also other information that could be output, depending on the referenced object (module vs. class/func via qualname).  For instance, a module's __file__ would be handy.  So, the output could have a "header" with the relevant info, followed by a blank line, and then the source code.

I suppose something like that could be added later with a commandline option, like "python -m inspect --info site", rather than being default behavior.  Then this issue can stay focused on the simpler idea. :)

Regardless, your proposal sounds good to me.  I don't see any other meaningful use for "-m inspect".
History
Date User Action Args
2013-08-02 04:53:11eric.snowsetrecipients: + eric.snow, ncoghlan
2013-08-02 04:53:11eric.snowsetmessageid: <1375419191.08.0.571987948186.issue18626@psf.upfronthosting.co.za>
2013-08-02 04:53:11eric.snowlinkissue18626 messages
2013-08-02 04:53:10eric.snowcreate